Answer in brief
CVE-2024-49573 records a Unknown severity vulnerability in sched/fair: Fix NEXT_BUDDY. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | 6.12 | Not reported |
| Linux/Linuxgeneric | >=152e11f6df293e816a6a37c69757033cdc72667d <5dbe6816c49197677a5ecce749bd99929da147da || >=152e11f6df293e816a6a37c69757033cdc72667d <493afbd187c4c9cc1642792c0d9ba400c3d6d90d | 5dbe6816c49197677a5ecce749bd99929da147da, 493afbd187c4c9cc1642792c0d9ba400c3d6d90d |
Published upstream
Jan 11, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-49573 records a Unknown severity vulnerability in sched/fair: Fix NEXT_BUDDY. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | 6.12 | Not reported |
| Linux/Linuxgeneric | >=152e11f6df293e816a6a37c69757033cdc72667d <5dbe6816c49197677a5ecce749bd99929da147da || >=152e11f6df293e816a6a37c69757033cdc72667d <493afbd187c4c9cc1642792c0d9ba400c3d6d90d | 5dbe6816c49197677a5ecce749bd99929da147da, 493afbd187c4c9cc1642792c0d9ba400c3d6d90d |
Published upstream
Jan 11, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.