CVE-2026-90326
Last modified
CVE-2026-90326 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: blk-cgroup: fix race between policy activation and blkg destruction When switching an IO scheduler on a block device, blkcg_activate_policy() allocates blkg_policy_data (pd) for all blkgs attached to the queue. However, blkcg_activate_policy() may race with concurrent blkcg deletion, leading to use-after-free and memory leak issues. The use-after-free occurs in the following race: T1 (blkcg_activate_policy): - Successfully allocates pd for blkg1 (loop0->queue, blkcgA) - Fails to allocate pd for blkg2 (loop0->queue, blkcgB) - Enters the enomem rollback path to release blkg1 resources T2 (blkcg deletion): - blkcgA is deleted concurrently - blkg1 is freed via blkg_free_workfn() - blkg1->pd is freed T1 (continued): - Rollback path accesses blkg1->pd->online after pd is freed - Triggers use-after-free In addition, blkg_free_workfn() frees pd before removing the blkg from q->blkg_list. This allows blkcg_activate_policy() to allocate a new pd for a blkg that is being destroyed, leaving the newly allocated pd unreachable when the blkg is finally freed. Fix these races by extending blkcg_mutex coverage to serialize blkcg_activate_policy() rollback and blkg destruction, ensuring pd lifecycle is synchronized with blkg list visibility..
Description
In the Linux kernel, the following vulnerability has been resolved: blk-cgroup: fix race between policy activation and blkg destruction When switching an IO scheduler on a block device, blkcg_activate_policy() allocates blkg_policy_data (pd) for all blkgs attached to the queue. However, blkcg_activate_policy() may race with concurrent blkcg deletion, leading to use-after-free and memory leak issues. The use-after-free occurs in the following race: T1 (blkcg_activate_policy): - Successfully allocates pd for blkg1 (loop0->queue, blkcgA) - Fails to allocate pd for blkg2 (loop0->queue, blkcgB) - Enters the enomem rollback path to release blkg1 resources T2 (blkcg deletion): - blkcgA is deleted concurrently - blkg1 is freed via blkg_free_workfn() - blkg1->pd is freed T1 (continued): - Rollback path accesses blkg1->pd->online after pd is freed - Triggers use-after-free In addition, blkg_free_workfn() frees pd before removing the blkg from q->blkg_list. This allows blkcg_activate_policy() to allocate a new pd for a blkg that is being destroyed, leaving the newly allocated pd unreachable when the blkg is finally freed. Fix these races by extending blkcg_mutex coverage to serialize blkcg_activate_policy() rollback and blkg destruction, ensuring pd lifecycle is synchronized with blkg list visibility.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 81c1188905f88b77743d1fdeeedfc8cb7b67787d, < b5dae1cd0d8368b4338430ff93403df67f0b8bcc; >= bfe46d2efe46c5c952f982e2ca94fe2ec5e58e2a, < 083b58373463a6e5ee60ecb135269348f68ad7df; >= f1c006f1c6850c14040f8337753a63119bba39b9, < ac34e655dffa74349d885a43d098115336f53842; >= f1c006f1c6850c14040f8337753a63119bba39b9, < 2cf9f50a38c1839e549a08e22aa35e8d69e2c8fd; >= f1c006f1c6850c14040f8337753a63119bba39b9, < 5313d4d41739b0cb63000747c97bb1217ac45f3e; >= 6.1.16, < 6.1.17; >= 6.2.3, < 6.2.4 |
| Linux | Linux | 6.3 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-90326?
How severe is CVE-2026-90326?
How do I fix CVE-2026-90326?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-90320In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-90321In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-90322In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90323In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90324In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-90325In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-90327In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90328In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90329In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-9033An unauthenticated attacker with network access to the capti…4.3
- CVE-2026-90330In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90331In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-90326?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
