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

Not scored Published

A local attacker can trigger a kernel panic in the Linux scheduler via cpuset configuration, causing a denial of service.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
None listed

What is GSD-2022-1005203?

GSD-2022-1005203 is a denial of service vulnerability in Kernel, published on 16 Sep 2022. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

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

This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven. This ID is fixed in Linux Kernel version v5.19.2 by commit f56607b44c9896e51678a7e8cdd3a5479f4b4548, it was introduced in version v3.19 by commit 7f51412a415d87ea8598d14722fb31e4f5701257. For more details please see the references link.

Which versions are affected by GSD-2022-1005203?

1 open source package ship an affected version, including Kernel.

PackageAffectedFixed in
Kernel LinuxAll versionsNone

How do I fix GSD-2022-1005203?

No fix has been published for GSD-2022-1005203 yet. Limit exposure of the affected software until one is available.

Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.

Is GSD-2022-1005203 being exploited?

There is no known exploitation of GSD-2022-1005203 in the wild and no public exploit code.

Sources

Is GSD-2022-1005203 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free