CVE-2024-49573Published Jan 11, 2025 · Jan 11Updated Oct 28
sched/fair: Fix NEXT_BUDDY
Linux
High7.0Fix available
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
Enabling NEXT_BUDDY in the Linux kernel scheduler can immediately trigger a warning in pick_next_entity(). The input does not describe an attacker, exploitation conditions, or any authentication or user-interaction requirements.
Engineers running Linux kernels with NEXT_BUDDY enabled should check their installations; affected versions are not specified.