sched: fix warning in sched_setaffinity
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.6.160, 6.12.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 8f9ea86fdf99b81458cc21fc1c591fcd4a0fa1f4 · fixed in d35130036d327b6c175d95db9ea8d64e1abd4a1b; From 8f9ea86fdf99b81458cc21fc1c591fcd4a0fa1f4 · fixed in 5c3fb75f538cfcb886f6dfeb497d99fc2f263ee6; From 8f9ea86fdf99b81458cc21fc1c591fcd4a0fa1f4 · fixed in 70ee7947a29029736a1a06c73a48ff37674a851b
- Linux Linux
6.2
- KernelLinux
From 6.2.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.5