From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-93071: media: bcm2835-unicam: Fix asc leaked in error/remove path
Date: Thu, 17 Sep 2026 17:15:50 +0100 [thread overview]
Message-ID: <2026091739-CVE-2026-93071-e1d4@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
media: bcm2835-unicam: Fix asc leaked in error/remove path
v4l2_async_nf_add_fwnode_remote() allocates the asc, which is freed when
v4l2_async_nf_cleanup() is called.
Call v4l2_async_nf_cleanup() properly in the driver paths.
Discovered with kmemleak after rmmod:
unreferenced object 0xffff000084526b80 (size 64):
comm "modprobe", pid 185, jiffies 4295013512
hex dump (first 32 bytes):
01 00 00 00 00 00 00 00 e8 0d ff bf 00 00 ff ff ................
40 83 bc 84 00 00 ff ff 60 83 bc 84 00 00 ff ff @.......`.......
backtrace (crc ac584083):
[<00000000ffb081a7>] kmemleak_alloc+0x38/0x44
[<00000000d2fd9301>] __kmalloc+0x1b0/0x250
[<000000004dd5354d>] __v4l2_async_nf_add_fwnode+0x28/0x9c
[<0000000067587657>] __v4l2_async_nf_add_fwnode_remote+0x3c/0x64
The Linux kernel CVE team has assigned CVE-2026-93071 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.10 with commit 392cd78d495f36c201eb5cc425b01017d493e094 and fixed in 6.12.110 with commit 5479372db364c80bb6bd59f640f5c31de3984bab
Issue introduced in 6.10 with commit 392cd78d495f36c201eb5cc425b01017d493e094 and fixed in 6.18.52 with commit 2c29cd408ef86e695acb2a5d4e00fa2f5695368d
Issue introduced in 6.10 with commit 392cd78d495f36c201eb5cc425b01017d493e094 and fixed in 7.2.6 with commit de9be39cefda1ecd762e6a913665c01f7bb18100
Issue introduced in 6.10 with commit 392cd78d495f36c201eb5cc425b01017d493e094 and fixed in 7.3-rc1 with commit 253c9659e25131b0169f718e7d094ac1aa0d9279
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-2026-93071
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/platform/broadcom/bcm2835-unicam.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/5479372db364c80bb6bd59f640f5c31de3984bab
https://git.kernel.org/stable/c/2c29cd408ef86e695acb2a5d4e00fa2f5695368d
https://git.kernel.org/stable/c/de9be39cefda1ecd762e6a913665c01f7bb18100
https://git.kernel.org/stable/c/253c9659e25131b0169f718e7d094ac1aa0d9279
reply other threads:[~2026-09-17 16:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026091739-CVE-2026-93071-e1d4@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.