NVD / CVE Program· CNA Linux

CVE-2024-43853: cgroup/cpuset: Prevent UAF in proc_cpuset_show()

Noroxi assessment

Priority: Monitor (action score 22/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Linux Linux 10aeaa47e4aa2432f29b3e5376df96d7dac5537a, 1be59c97c83ccd67a519d8a49486b3a8a73ca28a, 27d6dbdc6485d68075a0ebf8544d6425c1ed84bb; Azure Linux 3.0 ARM 6.6.47.1-1; Azure Linux 3.0 x64 6.6.47.1-1.

Low priority for now. Upgrade to Linux Linux 10aeaa47e4aa2432f29b3e5376df96d7dac5537a, 1be59c97c83ccd67a519d8a49486b3a8a73ca28a, 27d6dbdc6485d68075a0ebf8544d6425c1ed84bb; Azure Linux 3.0 ARM 6.6.47.1-1; Azure Linux 3.0 x64 6.6.47.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: cgroup/cpuset: Prevent UAF in proc_cpuset_show() An UAF can happen when /proc/cpuset is read as reported in [1]. This can be reproduced by the following methods: 1.add an mdelay(1000) before acquiring the cgroup_lock In the cgroup_path_ns function. 2.$cat /proc/<pid>/cpuset repeatly. 3.$mount -t cgroup -o cpuset cpuset /sys/fs/cgroup/cpuset/ $umount /sys/fs/cgroup/cpuset/ repeatly. The race that cause this bug can be shown as below: (umount) | (cat /proc/<pid>/cpuset) css_release | proc_cpuset_show css_release_work_fn | css = task_get_css(tsk, cpuset_cgrp_id); css_free_rwork_fn | cgroup_path_ns(css->cgroup, ...); cgroup_destroy_root | mutex_lock(&cgroup_mutex); rebind_subsystems | cgroup_free_root | | // cgrp was freed, UAF | cgroup_path_ns_locked(cgrp,..); When the cpuset is initialized, the root node top_cpuset.css.cgrp will point to &cgrp_dfl_root.cgrp. In cgroup v1, the mount operation will allocate cgroup_root, and top_cpuset.css.cgrp will point to the allocated &cgroup_root.cgrp. When the umount operation is executed, top_cpuset.css.cgrp will be rebound to &cgrp_dfl_root.cgrp. The problem is that when rebinding to cgrp_dfl_root, there are cases where the cgroup_root allocated by setting up the root for cgroup v1 is cached. This could lead to a Use-After-Free (UAF) if it is subsequently freed. The descendant cgroups of cgroup v1 can only be freed after the css is released. However, the css of the root will never be released, yet the cgroup_root should be freed when it is unmounted. This means that obtaining a reference to the css of the root does not guarantee that css.cgrp->root will not be freed. Fix this problem by using rcu_read_lock in proc_cpuset_show(). As cgroup_root is kfree_rcu after commit d23b5c577715 ("cgroup: Make operations on the cgroup root_list RCU safe"), css->cgroup won't be freed during the critical section. To call cgroup_path_ns_locked, css_set_lock is needed, so it is safe to replace task_get_css with task_css. [1] https://syzkaller.appspot.com/bug?extid=9b1ff7be974a403aa4cd

MediumCVSS 5.5 · v3.1—No exploit Fix available

BDU:2024-08346

Published: Aug 17, 2024
Updated: Aug 5, 2026
EPSS: 0.2% · 13th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 22 / 40 · 5.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 5.5
CNA · Linux: 7.0; 1.5 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

linux linux kernel4.6 and later · before 6.1.103
linux linux kernel6.2 and later · before 6.6.44
linux linux kernel6.7 and later · before 6.10.3

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

Linux Linux
- 4.6affected
- a79a908fd2b080977b45bf103184b81c9d11ad07 and later · before 27d6dbdc6485d68075a0ebf8544d6425c1ed84bbaffected · git
- a79a908fd2b080977b45bf103184b81c9d11ad07 and later · before 10aeaa47e4aa2432f29b3e5376df96d7dac5537aaffected · git
- a79a908fd2b080977b45bf103184b81c9d11ad07 and later · before 688325078a8b5badd6e07ae22b27cd04e9947aecaffected · git
- a79a908fd2b080977b45bf103184b81c9d11ad07 and later · before 4e8d6ac8fc9f843e940ab7389db8136634e07989affected · git
- a79a908fd2b080977b45bf103184b81c9d11ad07 and later · before 29a8d4e02fd4840028c38ceb1536cc8f82a257d4affected · git
- a79a908fd2b080977b45bf103184b81c9d11ad07 and later · before 96226fbed566f3f686f53a489a29846f2d538080affected · git
- a79a908fd2b080977b45bf103184b81c9d11ad07 and later · before 29ac1d238b3bf126af36037df80d7ecc4822341eaffected · git
- a79a908fd2b080977b45bf103184b81c9d11ad07 and later · before 1be59c97c83ccd67a519d8a49486b3a8a73ca28aaffected · git
- before 4.6not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	linux	before 6.1.106-1	6.1.106-1
Debian:13	linux	before 6.10.3-1	6.10.3-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now

Published before and after this one in the same product

← EarlierCVE-2024-43851Aug 17, 2024 · soc: xilinx: rename cpu_number1 to dummy_cpu_number
22Monitor
← EarlierCVE-2024-43852Aug 17, 2024 · hwmon: (ltc2991) re-order conditions to fix off by one bug
31Monitor
Later →CVE-2024-43854Aug 17, 2024 · block: initialize integrity buffer to zero before writing it to media
22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Linux Linux	10aeaa47e4aa2432f29b3e5376df96d7dac5537a	Vendor (CNA)
Linux Linux	1be59c97c83ccd67a519d8a49486b3a8a73ca28a	Vendor (CNA)
Linux Linux	27d6dbdc6485d68075a0ebf8544d6425c1ed84bb	Vendor (CNA)
Linux Linux	29a8d4e02fd4840028c38ceb1536cc8f82a257d4	Vendor (CNA)
Linux Linux	29ac1d238b3bf126af36037df80d7ecc4822341e	Vendor (CNA)
Linux Linux	4e8d6ac8fc9f843e940ab7389db8136634e07989	Vendor (CNA)
Linux Linux	688325078a8b5badd6e07ae22b27cd04e9947aec	Vendor (CNA)
Linux Linux	96226fbed566f3f686f53a489a29846f2d538080	Vendor (CNA)
Azure Linux 3.0 ARM	6.6.47.1-1 · kernel	Microsoft (MSRC)
Azure Linux 3.0 x64	6.6.47.1-1 · kernel	Microsoft (MSRC)
CBL Mariner 2.0 ARM	5.15.167.1-1 · kernel	Microsoft (MSRC)
CBL Mariner 2.0 x64	5.15.167.1-1 · kernel	Microsoft (MSRC)
debian:linux	6.1.106-1 · Debian:12	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: none
Integrity: none
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: None
Integrity impact: None
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

Fix✗ → ✓Sep 28, 2026, 10:08 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/10aeaa47e4aa2432f29b3e5376df96d7dac5537a

Show all references (9 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records