From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2025-40221: media: pci: mg4b: fix uninitialized iio scan data
Date: Thu, 4 Dec 2025 15:50:55 +0100 [thread overview]
Message-ID: <2025120454-CVE-2025-40221-e3f3@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
media: pci: mg4b: fix uninitialized iio scan data
Fix potential leak of uninitialized stack data to userspace by ensuring
that the `scan` structure is zeroed before use.
The Linux kernel CVE team has assigned CVE-2025-40221 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.7 with commit 0ab13674a9bd10514486cf1670d71dbd8afec421 and fixed in 6.12.54 with commit b7f82da7f86479cb6479a76ebe213ece7c77398f
Issue introduced in 6.7 with commit 0ab13674a9bd10514486cf1670d71dbd8afec421 and fixed in 6.17.4 with commit b792eba44494b4e6ab5006013335f9819f303b8b
Issue introduced in 6.7 with commit 0ab13674a9bd10514486cf1670d71dbd8afec421 and fixed in 6.18 with commit c0d3f6969bb4d72476cfe7ea9263831f1c283704
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-2025-40221
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/pci/mgb4/mgb4_trigger.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/b7f82da7f86479cb6479a76ebe213ece7c77398f
https://git.kernel.org/stable/c/b792eba44494b4e6ab5006013335f9819f303b8b
https://git.kernel.org/stable/c/c0d3f6969bb4d72476cfe7ea9263831f1c283704
reply other threads:[~2025-12-04 14:51 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=2025120454-CVE-2025-40221-e3f3@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.