[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025120400-CVE-2025-40232-a46a@gregkh>
Date: Thu, 4 Dec 2025 16:32:07 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-40232: rv: Fully convert enabled_monitors to use list_head as iterator
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
rv: Fully convert enabled_monitors to use list_head as iterator
The callbacks in enabled_monitors_seq_ops are inconsistent. Some treat the
iterator as struct rv_monitor *, while others treat the iterator as struct
list_head *.
This causes a wrong type cast and crashes the system as reported by Nathan.
Convert everything to use struct list_head * as iterator. This also makes
enabled_monitors consistent with available_monitors.
The Linux kernel CVE team has assigned CVE-2025-40232 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.17 with commit de090d1ccae1e191af4beb92964591c6e4f31f28 and fixed in 6.17.6 with commit 8948a0338d33c4a7ef1e0c439a3ad1d5fe9355ae
Issue introduced in 6.17 with commit de090d1ccae1e191af4beb92964591c6e4f31f28 and fixed in 6.18 with commit 103541e6a5854b08a25e4caa61e990af1009a52e
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-40232
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:
kernel/trace/rv/rv.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/8948a0338d33c4a7ef1e0c439a3ad1d5fe9355ae
https://git.kernel.org/stable/c/103541e6a5854b08a25e4caa61e990af1009a52e
Powered by blists - more mailing lists