CVE-2023-54208

EPSS 0.0%
  • Published: 2025-12-30T13:16:08.977

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

media: ov5675: Fix memleak in ov5675_init_controls()

There is a kmemleak when testing the media/i2c/ov5675.c with bpf mock
device:

AssertionError: unreferenced object 0xffff888107362160 (size 16):
comm “python3”, pid 277, jiffies 4294832798 (age 20.722s)
hex dump (first 16 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …………….
backtrace:
[] __kmalloc_node+0x44/0x1b0
[] kvmalloc_node+0x34/0x180
[] v4l2_ctrl_handler_init_class+0x11d/0x180
[videodev]
[] ov5675_probe+0x38b/0x897 [ov5675]
[] 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+0x386/0x540
[] of_i2c_register_device+0xf1/0x110
[] of_i2c_notify+0xfc/0x1f0

ov5675_init_controls() won’t clean all the allocated resources in fail
path, which may causes the memleaks. Add v4l2_ctrl_handler_free() to
prevent memleak.

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-54208

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

Description: In the Linux kernel, the following vulnerability has been resolved: media: ov5675: Fix memleak in ov5675_init_controls() There is a kmemleak when testing the media/i2c/ov5675.c with bpf mock device: AssertionError: unreferenced object 0xffff888107362160 (size 16): comm “python3”, pid 277, jiffies 4294832798 (age 20.722s) hex dump (first 16 bytes): 00 00 00 00 00 00 00 00 […]

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

Dec 30, 2025
Vulnerability Published

CVE details first published to NVD database

Dec 30, 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.