lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <2025011142-CVE-2024-49573-fa46@gregkh> Date: Sat, 11 Jan 2025 13:35:47 +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-49573: sched/fair: Fix NEXT_BUDDY Description =========== In the Linux kernel, the following vulnerability has been resolved: sched/fair: Fix NEXT_BUDDY Adam reports that enabling NEXT_BUDDY insta triggers a WARN in pick_next_entity(). Moving clear_buddies() up before the delayed dequeue bits ensures no ->next buddy becomes delayed. Further ensure no new ->next buddy ever starts as delayed. The Linux kernel CVE team has assigned CVE-2024-49573 to this issue. Affected and fixed versions =========================== Issue introduced in 6.12 with commit 152e11f6df293e816a6a37c69757033cdc72667d and fixed in 6.12.7 with commit 5dbe6816c49197677a5ecce749bd99929da147da Issue introduced in 6.12 with commit 152e11f6df293e816a6a37c69757033cdc72667d and fixed in 6.13-rc3 with commit 493afbd187c4c9cc1642792c0d9ba400c3d6d90d 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-49573 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/sched/fair.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/5dbe6816c49197677a5ecce749bd99929da147da https://git.kernel.org/stable/c/493afbd187c4c9cc1642792c0d9ba400c3d6d90d
Powered by blists - more mailing lists