VDB

CVE-2024-43853

CVE-2024-43853 PUBLISHED CVSS 7 HIGH

cgroup/cpuset: Prevent UAF in proc_cpuset_show()

Reported by linux · Published August 17, 2024

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

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
python3-perfAmazon Linux6.1.106-116.188.amzn2023
kernel-headersAmazon Linux4.14.355-271.569.amzn2
kernel-modules-extra-commonAmazon Linux6.1.106-116.188.amzn2023
kernel-develAmazon Linux4.14.355-271.569.amzn2
kernel-libbpf-develAmazon Linux6.1.106-116.188.amzn2023
LinuxLinux96226fbed566f3f686f53a489a29846f2d538080, 688325078a8b5badd6e07ae22b27cd04e9947aec, 4e8d6ac8fc9f843e940ab7389db8136634e07989, 29ac1d238b3bf126af36037df80d7ecc4822341e, 29a8d4e02fd4840028c38ceb1536cc8f82a257d4, 27d6dbdc6485d68075a0ebf8544d6425c1ed84bb, 1be59c97c83ccd67a519d8a49486b3a8a73ca28a

Risk scores

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

Affected products

VendorProductVersions
LinuxLinuxa79a908fd2b080977b45bf103184b81c9d11ad07, a79a908fd2b080977b45bf103184b81c9d11ad07, a79a908fd2b080977b45bf103184b81c9d11ad07
LinuxLinux4.6, 0, 4.19.321
amazon:2023python3-perf0
amazon:2kernel-headers0
amazon:2023kernel-modules-extra-common0
amazon:2kernel-devel0
amazon:2023kernel-libbpf-devel0
LinuxLinux*, *, *
amazon:2023kernel-headers0
amazon:2kernel0
amazon:2kernel-tools0
amazon:2023bpftool0
amazon:2023kernel-livepatch-6.1.106-116.1880
amazon:2023kernel-tools0
amazon:2023kernel-tools-devel0
amazon:2023kernel-modules-extra0
amazon:2python-perf0
linuxlinux_kernel4.6, 4.6, 4.6
amazon:2023kernel-libbpf0
amazon:2023kernel0

…and 6 more

Timeline

  • Aug 17, 2024 CVE Published
  • Aug 18, 2024 EPSS Score (30 in total, the first dated here)
  • Oct 4, 2024 Coalition ESS Score (13 in total, the first dated here)
  • Dec 16, 2025 PoC Published
  • Jan 5, 2026 Security Advisory (142 in total, the first dated here)
  • May 4, 2026 Distribution Patch (128 in total, the first dated here)

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2024-43853
vulnetix vdb fixes CVE-2024-43853

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2024-43853/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›