CVE-2023-53700
- Published: 2025-10-22T14:15:44.547
- Last modified: 1761167568
In the Linux kernel, the following vulnerability has been resolved:
media: max9286: Fix memleak in max9286_v4l2_register()
There is a kmemleak when testing the media/i2c/max9286.c with bpf mock
device:
kmemleak: 5 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
unreferenced object 0xffff88810defc400 (size 256):
comm “python3”, pid 278, jiffies 4294737563 (age 31.978s)
hex dump (first 32 bytes):
28 06 a7 0a 81 88 ff ff 00 fe 22 12 81 88 ff ff (………”…..
10 c4 ef 0d 81 88 ff ff 10 c4 ef 0d 81 88 ff ff …………….
backtrace:
[] __kmalloc_node+0x44/0x1b0
[] kvmalloc_node+0x34/0x180
[] v4l2_ctrl_new+0x325/0x10f0 [videodev]
[] v4l2_ctrl_new_std+0x16f/0x210 [videodev]
[] max9286_probe+0x76e/0xbff [max9286]
[] 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
max9286_v4l2_register() calls v4l2_ctrl_new_std(), but won’t free the
created v412_ctrl when fwnode_graph_get_endpoint_by_id() failed, which
causes the memleak. Call v4l2_ctrl_handler_free() to free the v412_ctrl.
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-53700
Description: In the Linux kernel, the following vulnerability has been resolved: media: max9286: Fix memleak in max9286_v4l2_register() There is a kmemleak when testing the media/i2c/max9286.c with bpf mock device: kmemleak: 5 new suspected memory leaks (see /sys/kernel/debug/kmemleak) unreferenced object 0xffff88810defc400 (size 256): comm “python3”, pid 278, jiffies 4294737563 (age 31.978s) hex dump (first 32 bytes): 28 […]
Exploit Difficulty: HARD
⏱️ Time to exploit: > 4 hours
🛠️ Required skills: Advanced security expertise
💰 Public exploits: Rare or not public
How to Fix:
- Check if you're running the affected product
- Update to the latest patched version
- If patching is not immediately possible: restrict network exposure, apply least-privilege access
- Test the fix in a staging environment first
- Review logs for signs of exploitation
- Monitor for IOCs (Indicators of Compromise)
- Enable automatic security updates
- Set up vulnerability monitoring
- Review and harden security configurations
Exploit Difficulty Assessment
Vulnerability Timeline
CVE details first published to NVD database
CVE details were updated
Added to this CVE tracking system
Detection Rules & IOCs
No specific detection rules generated for this vulnerability type.
No vendor/product data available.