We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.

Please see our statement on Data Privacy.

Crisp.chat (Helpdesk and Chat)

Ok

THREATINT
PUBLISHED

CVE-2022-50103

sched, cpuset: Fix dl_cpu_busy() panic due to empty cs->cpus_allowed



Description

In the Linux kernel, the following vulnerability has been resolved: sched, cpuset: Fix dl_cpu_busy() panic due to empty cs->cpus_allowed With cgroup v2, the cpuset's cpus_allowed mask can be empty indicating that the cpuset will just use the effective CPUs of its parent. So cpuset_can_attach() can call task_can_attach() with an empty mask. This can lead to cpumask_any_and() returns nr_cpu_ids causing the call to dl_bw_of() to crash due to percpu value access of an out of bound CPU value. For example: [80468.182258] BUG: unable to handle page fault for address: ffffffff8b6648b0 : [80468.191019] RIP: 0010:dl_cpu_busy+0x30/0x2b0 : [80468.207946] Call Trace: [80468.208947] cpuset_can_attach+0xa0/0x140 [80468.209953] cgroup_migrate_execute+0x8c/0x490 [80468.210931] cgroup_update_dfl_csses+0x254/0x270 [80468.211898] cgroup_subtree_control_write+0x322/0x400 [80468.212854] kernfs_fop_write_iter+0x11c/0x1b0 [80468.213777] new_sync_write+0x11f/0x1b0 [80468.214689] vfs_write+0x1eb/0x280 [80468.215592] ksys_write+0x5f/0xe0 [80468.216463] do_syscall_64+0x5c/0x80 [80468.224287] entry_SYSCALL_64_after_hwframe+0x44/0xae Fix that by using effective_cpus instead. For cgroup v1, effective_cpus is the same as cpus_allowed. For v2, effective_cpus is the real cpumask to be used by tasks within the cpuset anyway. Also update task_can_attach()'s 2nd argument name to cs_effective_cpus to reflect the change. In addition, a check is added to task_can_attach() to guard against the possibility that cpumask_any_and() may return a value >= nr_cpu_ids.

Reserved 2025-06-18 | Published 2025-06-18 | Updated 2025-06-18 | Assigner Linux

Product status

Default status
unaffected

7f51412a415d87ea8598d14722fb31e4f5701257 before 336626564b58071b8980a4e6a31a8f5d92705d9b
affected

7f51412a415d87ea8598d14722fb31e4f5701257 before 147f66d22f58712dce7ccdd6a1f6cb3ee8042df4
affected

7f51412a415d87ea8598d14722fb31e4f5701257 before 357f3f0e522a6ce1ce4a571cb780d9861d53bec7
affected

7f51412a415d87ea8598d14722fb31e4f5701257 before f56607b44c9896e51678a7e8cdd3a5479f4b4548
affected

7f51412a415d87ea8598d14722fb31e4f5701257 before b6e8d40d43ae4dec00c8fea2593eeea3114b8f44
affected

Default status
affected

3.19
affected

Any version before 3.19
unaffected

5.10.137
unaffected

5.15.61
unaffected

5.18.18
unaffected

5.19.2
unaffected

6.0
unaffected

References

git.kernel.org/...c/336626564b58071b8980a4e6a31a8f5d92705d9b

git.kernel.org/...c/147f66d22f58712dce7ccdd6a1f6cb3ee8042df4

git.kernel.org/...c/357f3f0e522a6ce1ce4a571cb780d9861d53bec7

git.kernel.org/...c/f56607b44c9896e51678a7e8cdd3a5479f4b4548

git.kernel.org/...c/b6e8d40d43ae4dec00c8fea2593eeea3114b8f44

cve.org (CVE-2022-50103)

nvd.nist.gov (CVE-2022-50103)

Download JSON

Share this page
https://cve.threatint.eu/CVE/CVE-2022-50103

Support options

Helpdesk Chat, Email, Knowledgebase