[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025063052-CVE-2025-38087-cd0f@gregkh>
Date: Mon, 30 Jun 2025 09:29:51 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-38087: net/sched: fix use-after-free in taprio_dev_notifier
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
net/sched: fix use-after-free in taprio_dev_notifier
Since taprio’s taprio_dev_notifier() isn’t protected by an
RCU read-side critical section, a race with advance_sched()
can lead to a use-after-free.
Adding rcu_read_lock() inside taprio_dev_notifier() prevents this.
The Linux kernel CVE team has assigned CVE-2025-38087 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.3 with commit fed87cc6718ad5f80aa739fee3c5979a8b09d3a6 and fixed in 6.6.95 with commit 8c5713ce1ced75f9e9ed5c642ea3d2ba06ead69c
Issue introduced in 6.3 with commit fed87cc6718ad5f80aa739fee3c5979a8b09d3a6 and fixed in 6.12.35 with commit 8a008c89e5e5c5332e4c0a33d707db9ddd529f8a
Issue introduced in 6.3 with commit fed87cc6718ad5f80aa739fee3c5979a8b09d3a6 and fixed in 6.15.4 with commit b1547d28ba468bc3b88764efd13e4319bab63be8
Issue introduced in 6.3 with commit fed87cc6718ad5f80aa739fee3c5979a8b09d3a6 and fixed in 6.16-rc3 with commit b160766e26d4e2e2d6fe2294e0b02f92baefcec5
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-38087
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:
net/sched/sch_taprio.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/8c5713ce1ced75f9e9ed5c642ea3d2ba06ead69c
https://git.kernel.org/stable/c/8a008c89e5e5c5332e4c0a33d707db9ddd529f8a
https://git.kernel.org/stable/c/b1547d28ba468bc3b88764efd13e4319bab63be8
https://git.kernel.org/stable/c/b160766e26d4e2e2d6fe2294e0b02f92baefcec5
Powered by blists - more mailing lists