CVE-2023-54107
- Source
- https://cve.org/CVERecord?id=CVE-2023-54107
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-54107.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2023-54107
- Downstream
- Related
- Published
- 2025-12-24T13:06:31Z
- Modified
- 2026-08-12T03:51:44Z
- Severity
-
- 7.8 (High) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H CVSS Calculator
- Summary
- blk-cgroup: dropping parent refcount after pd_free_fn() is done
- Details
-
In the Linux kernel, the following vulnerability has been resolved:
blk-cgroup: dropping parent refcount after pd_free_fn() is done
Some cgroup policies will access parent pd through child pd even after pd_offline_fn() is done. If pd_free_fn() for parent is called before child, then UAF can be triggered. Hence it's better to guarantee the order of pd_free_fn().
Currently refcount of parent blkg is dropped in __blkg_release(), which is before pd_free_fn() is called in blkg_free_work_fn() while blkg_free_work_fn() is called asynchronously.
This patch make sure pd_free_fn() called from removing cgroup is ordered by delaying dropping parent refcount after calling pd_free_fn() for child.
BTW, pd_free_fn() will also be called from blkcg_deactivate_policy() from deleting device, and following patches will guarantee the order.
- Database specific
{ "cna_assigner": "Linux", "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/54xxx/CVE-2023-54107.json" }- References