LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53700: media: max9286: Fix memleak in max9286_v4l2_register()

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: [<00000000191de6a7>] __kmalloc_node+0x44/0x1b0 [<000000002f4912b7>] kvmalloc_node+0x34/0x180 [<0000000057dc4cae>] v4l2_ctrl_new+0x325/0x10f0 [videodev] [<0000000026030272>] v4l2_ctrl_new_std+0x16f/0x210 [videodev] [<00000000f0d9ea2f>] max9286_probe+0x76e/0xbff [max9286] [<00000000ea8f6455>] i2c_device_probe+0x28d/0x680 [<0000000087529af3>] really_probe+0x17c/0x3f0 [<00000000b08be526>] __driver_probe_device+0xe3/0x170 [<000000004382edea>] driver_probe_device+0x49/0x120 [<000000007bde528a>] __device_attach_driver+0xf7/0x150 [<000000009f9c6ab4>] bus_for_each_drv+0x114/0x180 [<00000000c8aaf588>] __device_attach+0x1e5/0x2d0 [<0000000041cc06b9>] bus_probe_device+0x126/0x140 [<000000002309860d>] device_add+0x810/0x1130 [<000000002827bf98>] i2c_new_client_device+0x359/0x4f0 [<00000000593bdc85>] 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.

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-53700 is a Linux kernel memory leak in the MAX9286 media driver. It occurs during device registration when an endpoint lookup fails after a V4L2 control was allocated. The available sources do not show active exploitation, remote attackability, or business-impact severity scoring.

Executive priority

Track and remediate through normal kernel maintenance unless affected embedded camera systems are business-critical. There is no cited active exploitation or CVSS score in the provided evidence, so urgency is lower than remotely exploitable kernel flaws.

Technical view

In media/i2c/max9286.c, max9286_v4l2_register() calls v4l2_ctrl_new_std() but failed to release the created control on an error path from fwnode_graph_get_endpoint_by_id(). The kernel fix frees the V4L2 control handler to remove the leak.

Likely exposure

Exposure appears limited to Linux systems using or probing the MAX9286 media driver, including embedded, automotive, camera, or test environments. General servers are unlikely to be exposed unless this driver is present and reachable through their kernel configuration and hardware or mock-device setup.

Exploitation context

The source bundle reports detection through kmemleak testing with a BPF mock device. It does not cite KEV listing, public exploitation, exploit code, privilege impact, or remote triggering evidence. Treat exploitation status as not demonstrated from the provided sources.

Researcher notes

The bug is an error-path resource leak in max9286_v4l2_register(). The key validation question is whether a target can reach the failing endpoint path with the driver loaded. Source evidence is limited to the CVE record and kernel stable commits.

Mitigation direction

  • Check whether deployed kernels include the MAX9286 media driver.
  • Update to vendor kernels containing the referenced stable fixes.
  • Prioritize embedded or camera systems that load this driver.
  • Follow distribution or device-vendor advisories for exact fixed builds.

Validation and detection

  • Confirm running kernel versions against vendor fixed-package guidance.
  • Check kernel config or modules for MAX9286 driver presence.
  • Review device trees or hardware inventory for MAX9286 usage.
  • Use vendor security advisories to confirm backported fix status.
Prepared
Confidence
medium
Sources
7

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-53700 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
6Source 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
LinuxLinux66d8c9d2422da21ed41f75c03ba0685987b65fe0, 66d8c9d2422da21ed41f75c03ba0685987b65fe0, 66d8c9d2422da21ed41f75c03ba0685987b65fe0, 66d8c9d2422da21ed41f75c03ba0685987b65fe0, 66d8c9d2422da21ed41f75c03ba0685987b65fe0unaffected
LinuxLinux5.9, 0, 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.