linux-cve-announce - CVE-2023-53700: media: max9286: Fix memleak in max9286_v4l2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025102211-CVE-2023-53700-9753@gregkh>
Date: Wed, 22 Oct 2025 15:24:39 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-53700: media: max9286: Fix memleak in max9286_v4l2_register()

From: Greg Kroah-Hartman <gregkh@...nel.org>

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

The Linux kernel CVE team has assigned CVE-2023-53700 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 5.9 with commit 66d8c9d2422da21ed41f75c03ba0685987b65fe0 and fixed in 5.10.173 with commit 505ff3a0c5951684c3a43094ca4c1a74683d5681
	Issue introduced in 5.9 with commit 66d8c9d2422da21ed41f75c03ba0685987b65fe0 and fixed in 5.15.99 with commit 5897fe3ebe8252993579e1bee715ebfe5504e052
	Issue introduced in 5.9 with commit 66d8c9d2422da21ed41f75c03ba0685987b65fe0 and fixed in 6.1.16 with commit 724039e013b34f46344abdbf8c74e6a65a828327
	Issue introduced in 5.9 with commit 66d8c9d2422da21ed41f75c03ba0685987b65fe0 and fixed in 6.2.3 with commit 5e31213fa017c20ccc989033a5f4a626473aa2ca
	Issue introduced in 5.9 with commit 66d8c9d2422da21ed41f75c03ba0685987b65fe0 and fixed in 6.3 with commit 8636c5fc7658c7c6299fb8b352d24ea4b9ba99e2

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2023-53700
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/media/i2c/max9286.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/505ff3a0c5951684c3a43094ca4c1a74683d5681
	https://git.kernel.org/stable/c/5897fe3ebe8252993579e1bee715ebfe5504e052
	https://git.kernel.org/stable/c/724039e013b34f46344abdbf8c74e6a65a828327
	https://git.kernel.org/stable/c/5e31213fa017c20ccc989033a5f4a626473aa2ca
	https://git.kernel.org/stable/c/8636c5fc7658c7c6299fb8b352d24ea4b9ba99e2