CVE-2022-50103 [High] | Out-of-bounds Read in Linux Kernel

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.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-04-14	0.02%	0.06%	+0.05%
2	2025-06-18	—	0.02%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-04-14

0.02%

0.06%

+0.05%

2025-06-18

—

0.02%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
7.1	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	5.2	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

7.1

3.1

HIGH

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

5.2

[email protected]

OS Trackers for CVE-2022-50103

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2022-50103 not yet assigned priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2022-50103
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2022-50103
`suse`	medium	—	https://www.suse.com/security/cve/CVE-2022-50103/
`ubuntu`	medium	CVE-2022-50103 medium priority: Ubuntu including 158 source packages (linux, linux-allwinner-5.19, …), 1551 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 1145, ignored 150, released 114, not-affected 100, needed 41, needs-triage 1.	https://ubuntu.com/security/CVE-2022-50103

Affected software / configurations for CVE-2022-50103

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 3.19, < 5.10.137	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.11, < 5.15.61	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.16, < 5.18.18	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.19, < 5.19.2	cpe:2.3:o:linux:linux_kernel::::::::

References for CVE-2022-50103

URL	Tags
https://git.kernel.org/stable/c/147f66d22f58712dce7ccdd6a1f6cb3ee8042df4	Patch
https://git.kernel.org/stable/c/336626564b58071b8980a4e6a31a8f5d92705d9b	Patch
https://git.kernel.org/stable/c/357f3f0e522a6ce1ce4a571cb780d9861d53bec7	Patch
https://git.kernel.org/stable/c/b6e8d40d43ae4dec00c8fea2593eeea3114b8f44	Patch
https://git.kernel.org/stable/c/f56607b44c9896e51678a7e8cdd3a5479f4b4548	Patch

URL

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

Exploit prediction scoring system (EPSS) score for CVE-2022-50103

Common vulnerability scoring system (CVSS) metrics for CVE-2022-50103

Weakness enumeration for CVE-2022-50103

OS Trackers for CVE-2022-50103

Affected software / configurations for CVE-2022-50103

References for CVE-2022-50103