CVE-2023-53637

  • Published: 2025-10-07T16:15:46.883

In the Linux kernel, the following vulnerability has been resolved:

media: i2c: ov772x: Fix memleak in ov772x_probe()

A memory leak was reported when testing ov772x with bpf mock device:

AssertionError: unreferenced object 0xffff888109afa7a8 (size 8):
comm “python3”, pid 279, jiffies 4294805921 (age 20.681s)
hex dump (first 8 bytes):
80 22 88 15 81 88 ff ff .”……
backtrace:
[] __kmalloc_node+0x44/0x1b0
[] kvmalloc_node+0x34/0x180
[] v4l2_ctrl_handler_init_class+0x11d/0x180 [videodev]
[] ov772x_probe+0x1c3/0x68c [ov772x]
[] i2c_device_probe+0x28d/0x680
[] really_probe+0x17c/0x3f0
[] __driver_probe_device+0xe3/0x170
[] driver_probe_device+0x49/0x120
[] __device_attach_driver+0xf7/0x150
[] bus_for_each_drv+0x114/0x180
[] __device_attach+0x1e5/0x2d0
[] bus_probe_device+0x126/0x140
[] device_add+0x810/0x1130
[] i2c_new_client_device+0x359/0x4f0
[] of_i2c_register_device+0xf1/0x110
[] of_i2c_notify+0x100/0x160
unreferenced object 0xffff888119825c00 (size 256):
comm “python3”, pid 279, jiffies 4294805921 (age 20.681s)
hex dump (first 32 bytes):
00 b4 a5 17 81 88 ff ff 00 5e 82 19 81 88 ff ff ………^……
10 5c 82 19 81 88 ff ff 10 5c 82 19 81 88 ff ff …………..
backtrace:
[] __kmalloc_node+0x44/0x1b0
[] kvmalloc_node+0x34/0x180
[] v4l2_ctrl_new.cold+0x19b/0x86f [videodev]
[] v4l2_ctrl_new_std+0x16f/0x210 [videodev]
[] ov772x_probe+0x1fa/0x68c [ov772x]
[] i2c_device_probe+0x28d/0x680
[] really_probe+0x17c/0x3f0
[] __driver_probe_device+0xe3/0x170
[] driver_probe_device+0x49/0x120
[] __device_attach_driver+0xf7/0x150
[] bus_for_each_drv+0x114/0x180
[] __device_attach+0x1e5/0x2d0
[] bus_probe_device+0x126/0x140
[] device_add+0x810/0x1130
[] i2c_new_client_device+0x359/0x4f0
[] of_i2c_register_device+0xf1/0x110

The reason is that if priv->hdl.error is set, ov772x_probe() jumps to the
error_mutex_destroy without doing v4l2_ctrl_handler_free(), and all
resources allocated in v4l2_ctrl_handler_init() and v4l2_ctrl_new_std()
are leaked.

Related CVE by CWE

No related CWE found.

Top CVE for Vendor

No vendor taxonomy on this entry.

Recently Exploited Similar Vulnerabilities

No recent KEV-listed items for this vendor/product.

How to fix CVE-2023-53637

CVE-2023-53637 is a unknown severity vulnerability affecting the affected product.

Description: In the Linux kernel, the following vulnerability has been resolved: media: i2c: ov772x: Fix memleak in ov772x_probe() A memory leak was reported when testing ov772x with bpf mock device: AssertionError: unreferenced object 0xffff888109afa7a8 (size 8): comm “python3”, pid 279, jiffies 4294805921 (age 20.681s) hex dump (first 8 bytes): 80 22 88 15 81 88 ff […]

Exploit Difficulty: HARD
⏱️ Time to exploit: > 4 hours
🛠️ Required skills: Advanced security expertise
💰 Public exploits: Rare or not public

How to Fix:

1 Identify affected systems

- Check if you're running the affected product

2 Immediate actions

- Update to the latest patched version
- If patching is not immediately possible: restrict network exposure, apply least-privilege access

3 Verification

- Test the fix in a staging environment first
- Review logs for signs of exploitation
- Monitor for IOCs (Indicators of Compromise)

4 Long-term prevention

- Enable automatic security updates
- Set up vulnerability monitoring
- Review and harden security configurations

Exploit Difficulty Assessment

HARD
⏱️ Time to Exploit: > 4 hours
🛠️ Skills Required: Advanced security expertise
💰 Public Exploits: Rare or not public

Vulnerability Timeline

Oct 07, 2025
Vulnerability Published

CVE details first published to NVD database

Nov 12, 2025
Imported to Database

Added to this CVE tracking system

Detection Rules & IOCs

No specific detection rules generated for this vulnerability type.

No vendor/product data available.