Answer in brief
CVE-2024-41932 records a Unknown severity vulnerability in sched: fix warning in sched_setaffinity. 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 | >=8f9ea86fdf99b81458cc21fc1c591fcd4a0fa1f4 <d35130036d327b6c175d95db9ea8d64e1abd4a1b || >=8f9ea86fdf99b81458cc21fc1c591fcd4a0fa1f4 <5c3fb75f538cfcb886f6dfeb497d99fc2f263ee6 || >=8f9ea86fdf99b81458cc21fc1c591fcd4a0fa1f4 <70ee7947a29029736a1a06c73a48ff37674a851b | d35130036d327b6c175d95db9ea8d64e1abd4a1b, 5c3fb75f538cfcb886f6dfeb497d99fc2f263ee6, 70ee7947a29029736a1a06c73a48ff37674a851b |
| Linux/Linuxgeneric | 6.2 | Not reported |
Published upstream
Jan 11, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 21, 2026
In the Linux kernel, the following vulnerability has been resolved: sched: fix warning in sched_setaffinity Commit 8f9ea86fdf99b added some logic to sched_setaffinity that included a WARN when a per-task affinity assignment races with a cpuset update. Specifically, we can have a race where a cpuset update results in the task affinity no longer being a subset of the cpuset. That's fine; we have a fallback to instead use the cpuset mask. However, we have a WARN set up that will trigger if the cpuset mask has no overlap at all with the requested task affinity. This shouldn't be a warning condition; its trivial to create this condition. Reproduced the warning by the following setup: - $PID inside a cpuset cgroup - another thread repeatedly switching the cpuset cpus from 1-2 to just 1 - another thread repeatedly setting the $PID affinity (via taskset) to 2
Quoted source text, attributed separately from HOL analysis.