LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54208: media: ov5675: Fix memleak in ov5675_init_controls()

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: [<00000000abe7d67c>] __kmalloc_node+0x44/0x1b0 [<000000008a725aac>] kvmalloc_node+0x34/0x180 [<000000009a53cd11>] v4l2_ctrl_handler_init_class+0x11d/0x180 [videodev] [<0000000055b46db0>] ov5675_probe+0x38b/0x897 [ov5675] [<00000000153d886c>] i2c_device_probe+0x28d/0x680 [<000000004afb7e8f>] really_probe+0x17c/0x3f0 [<00000000ff2f18e4>] __driver_probe_device+0xe3/0x170 [<000000000a001029>] driver_probe_device+0x49/0x120 [<00000000e39743c7>] __device_attach_driver+0xf7/0x150 [<00000000d32fd070>] bus_for_each_drv+0x114/0x180 [<000000009083ac41>] __device_attach+0x1e5/0x2d0 [<0000000015b4a830>] bus_probe_device+0x126/0x140 [<000000007813deaf>] device_add+0x810/0x1130 [<000000007becb867>] i2c_new_client_device+0x386/0x540 [<000000007f9cf4b4>] of_i2c_register_device+0xf1/0x110 [<00000000ebfdd032>] 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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2023-54208 is a Linux kernel memory leak in the OV5675 camera sensor driver. The reported leak occurs during driver initialization failure handling, not during normal remote network activity. Business urgency is mainly for devices that run affected Linux kernels and include or enable this camera driver.

Executive priority

Treat this as a targeted kernel maintenance item, not an emergency. Patch through normal kernel update channels, with faster handling for products or fleets that ship camera-enabled Linux images using the OV5675 driver.

Technical view

The issue is in media/i2c/ov5675.c. ov5675_init_controls() did not free all allocated V4L2 control handler resources on an error path, causing a kernel memory leak. The fix adds v4l2_ctrl_handler_free() on failure paths. Public sources list Linux kernel stable fixes for multiple branches.

Likely exposure

Exposure appears limited to Linux systems using affected kernel versions where the OV5675 media I2C camera sensor driver is present and can be probed. Servers without this driver or hardware are less likely to be affected, but embedded, laptop, tablet, or camera-enabled Linux builds should be checked.

Exploitation context

The source bundle reports a kmemleak found during testing with a BPF mock device. It does not show active exploitation, a public exploit, privilege escalation, data exposure, or remote attack behavior. KEV status is false.

Researcher notes

Evidence is narrow: a kernel memory leak on an initialization failure path, detected by kmemleak during test probing. The bundle provides fix commits but no CVSS, CWE, exploitability analysis, or distro-specific advisory detail. Avoid assuming broad impact beyond affected Linux kernels and the driver path.

Mitigation direction

  • Update to a vendor-supported Linux kernel containing the referenced stable fixes.
  • Prioritize embedded and camera-enabled Linux builds that include the OV5675 driver.
  • If patching is delayed, check vendor guidance for supported mitigations.
  • Disable or exclude the OV5675 driver only if the platform does not require it.

Validation and detection

  • Inventory Linux kernel versions across affected device fleets.
  • Check whether the OV5675 driver is built, packaged, or loaded.
  • Confirm the running kernel includes the relevant stable fix commit.
  • Review device logs for repeated OV5675 probe or initialization failures.
Prepared
Confidence
medium
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-54208 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
7Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxbf27502b1f3bf8095bf81736e506d354a2ce9ec4, bf27502b1f3bf8095bf81736e506d354a2ce9ec4, bf27502b1f3bf8095bf81736e506d354a2ce9ec4, bf27502b1f3bf8095bf81736e506d354a2ce9ec4, bf27502b1f3bf8095bf81736e506d354a2ce9ec4, bf27502b1f3bf8095bf81736e506d354a2ce9ec4unaffected
LinuxLinux5.4, 0, 5.4.235, 5.10.173, 5.15.99, 6.1.16, 6.2.3, 6.3affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.