From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2025-40197: media: mc: Clear minor number before put device
Date: Wed, 12 Nov 2025 17:01:00 -0500 [thread overview]
Message-ID: <2025111246-CVE-2025-40197-e5de@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
media: mc: Clear minor number before put device
The device minor should not be cleared after the device is released.
The Linux kernel CVE team has assigned CVE-2025-40197 to this issue.
Affected and fixed versions
===========================
Fixed in 5.4.301 with commit dd156f44ea82cc249f46c519eed3b2f8983c8002
Fixed in 5.10.246 with commit 64dbc6f50ce92b7da203b1bcdd96a370bbc9b74d
Fixed in 5.15.195 with commit 5d327391f9fafeb0938be4fc538dd0bd54a0b2ef
Fixed in 6.1.157 with commit 8f52c7f38f0f2ee2afc331e6b873acba5e9490a8
Fixed in 6.6.113 with commit 7bd4e5367d0940ccec4d7546bb6bd019ab2c71aa
Fixed in 6.12.54 with commit 7db47e737128b3585ae679b709b85f3f44cd8750
Fixed in 6.17.4 with commit ac01416d477c2dc6016782635ae022f8cc634a29
Fixed in 6.18-rc1 with commit 8cfc8cec1b4da88a47c243a11f384baefd092a50
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-40197
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/mc/mc-devnode.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/dd156f44ea82cc249f46c519eed3b2f8983c8002
https://git.kernel.org/stable/c/64dbc6f50ce92b7da203b1bcdd96a370bbc9b74d
https://git.kernel.org/stable/c/5d327391f9fafeb0938be4fc538dd0bd54a0b2ef
https://git.kernel.org/stable/c/8f52c7f38f0f2ee2afc331e6b873acba5e9490a8
https://git.kernel.org/stable/c/7bd4e5367d0940ccec4d7546bb6bd019ab2c71aa
https://git.kernel.org/stable/c/7db47e737128b3585ae679b709b85f3f44cd8750
https://git.kernel.org/stable/c/ac01416d477c2dc6016782635ae022f8cc634a29
https://git.kernel.org/stable/c/8cfc8cec1b4da88a47c243a11f384baefd092a50
reply other threads:[~2025-11-12 22:01 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=2025111246-CVE-2025-40197-e5de@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.