| From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2024-41932: sched: fix warning in sched_setaffinity |
| |
| Description |
| =========== |
| |
| 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 |
| |
| The Linux kernel CVE team has assigned CVE-2024-41932 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.2 with commit 8f9ea86fdf99b81458cc21fc1c591fcd4a0fa1f4 and fixed in 6.12.5 with commit 5c3fb75f538cfcb886f6dfeb497d99fc2f263ee6 |
| Issue introduced in 6.2 with commit 8f9ea86fdf99b81458cc21fc1c591fcd4a0fa1f4 and fixed in 6.13 with commit 70ee7947a29029736a1a06c73a48ff37674a851b |
| |
| Please see https://www.kernel.org for a full list of currently supported |
| kernel versions by the kernel community. |
| |
| Unaffected versions might change over time as fixes are backported to |
| older supported kernel versions. The official CVE entry at |
| https://cve.org/CVERecord/?id=CVE-2024-41932 |
| will be updated if fixes are backported, please check that for the most |
| up to date information about this issue. |
| |
| |
| Affected files |
| ============== |
| |
| The file(s) affected by this issue are: |
| kernel/sched/syscalls.c |
| |
| |
| Mitigation |
| ========== |
| |
| The Linux kernel CVE team recommends that you update to the latest |
| stable kernel version for this, and many other bugfixes. Individual |
| changes are never tested alone, but rather are part of a larger kernel |
| release. Cherry-picking individual commits is not recommended or |
| supported by the Linux kernel community at all. If however, updating to |
| the latest release is impossible, the individual changes to resolve this |
| issue can be found at these commits: |
| https://git.kernel.org/stable/c/5c3fb75f538cfcb886f6dfeb497d99fc2f263ee6 |
| https://git.kernel.org/stable/c/70ee7947a29029736a1a06c73a48ff37674a851b |
