CVE-2024-41932: sched: fix warning in sched_setaffinity
In the Linux kernel, the following vulnerability has been resolved:
sched: fix warning in schedsetaffinity
Commit 8f9ea86fdf99b added some logic to schedsetaffinity 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
Other sources
This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.
— Launchpad
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-41932?
CVE-2024-41932 has been classified as a low-severity issue.
How do I fix CVE-2024-41932?
To fix CVE-2024-41932, update the Linux kernel to the latest stable version that includes the vulnerability resolution.
What does CVE-2024-41932 affect?
CVE-2024-41932 affects the Linux kernel, specifically the sched_setaffinity function.
Is CVE-2024-41932 remotely exploitable?
CVE-2024-41932 is not considered to be remotely exploitable as it pertains to local task management.
What is the impact of CVE-2024-41932?
The impact of CVE-2024-41932 could lead to warning messages when tasks compete for CPU affinity during cpuset updates.