[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2024110557-CVE-2024-50127-c0b5@gregkh>
Date: Tue, 5 Nov 2024 18:11:16 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-50127: net: sched: fix use-after-free in taprio_change()
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
net: sched: fix use-after-free in taprio_change()
In 'taprio_change()', 'admin' pointer may become dangling due to sched
switch / removal caused by 'advance_sched()', and critical section
protected by 'q->current_entry_lock' is too small to prevent from such
a scenario (which causes use-after-free detected by KASAN). Fix this
by prefer 'rcu_replace_pointer()' over 'rcu_assign_pointer()' to update
'admin' immediately before an attempt to schedule freeing.
The Linux kernel CVE team has assigned CVE-2024-50127 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.2 with commit a3d43c0d56f1 and fixed in 5.15.170 with commit 999612996df2
Issue introduced in 5.2 with commit a3d43c0d56f1 and fixed in 6.1.115 with commit fe371f084073
Issue introduced in 5.2 with commit a3d43c0d56f1 and fixed in 6.6.59 with commit 0d4c0d2844e4
Issue introduced in 5.2 with commit a3d43c0d56f1 and fixed in 6.11.6 with commit 2240f9376f20
Issue introduced in 5.2 with commit a3d43c0d56f1 and fixed in 6.12-rc5 with commit f504465970ae
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-2024-50127
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/999612996df28d81f163dad530d7f8026e03aec6
https://git.kernel.org/stable/c/fe371f084073e8672a2d7d46b335c3c060d1e301
https://git.kernel.org/stable/c/0d4c0d2844e4eac3aed647f948fd7e60eea56a61
https://git.kernel.org/stable/c/2240f9376f20f8b6463232b4ca7292569217237f
https://git.kernel.org/stable/c/f504465970aebb2467da548f7c1efbbf36d0f44b
Powered by blists - more mailing lists