| From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.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 a3d43c0d56f1b94e74963a2fbadfb70126d92213 and fixed in 5.4.285 with commit 2f868ce6013548a713c431c679ef73747a66fcf3 |
| Issue introduced in 5.2 with commit a3d43c0d56f1b94e74963a2fbadfb70126d92213 and fixed in 5.10.229 with commit 8a283a19026aaae8a773fd8061263cfa315b127f |
| Issue introduced in 5.2 with commit a3d43c0d56f1b94e74963a2fbadfb70126d92213 and fixed in 5.15.170 with commit 999612996df28d81f163dad530d7f8026e03aec6 |
| Issue introduced in 5.2 with commit a3d43c0d56f1b94e74963a2fbadfb70126d92213 and fixed in 6.1.115 with commit fe371f084073e8672a2d7d46b335c3c060d1e301 |
| Issue introduced in 5.2 with commit a3d43c0d56f1b94e74963a2fbadfb70126d92213 and fixed in 6.6.59 with commit 0d4c0d2844e4eac3aed647f948fd7e60eea56a61 |
| Issue introduced in 5.2 with commit a3d43c0d56f1b94e74963a2fbadfb70126d92213 and fixed in 6.11.6 with commit 2240f9376f20f8b6463232b4ca7292569217237f |
| Issue introduced in 5.2 with commit a3d43c0d56f1b94e74963a2fbadfb70126d92213 and fixed in 6.12 with commit f504465970aebb2467da548f7c1efbbf36d0f44b |
| |
| 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/2f868ce6013548a713c431c679ef73747a66fcf3 |
| https://git.kernel.org/stable/c/8a283a19026aaae8a773fd8061263cfa315b127f |
| 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 |
