PoC Monitor
← All CVEs
CVE-2026-90326published 17 Sep 2026 16:08 UTCData: JSON · API

Linux

blk-cgroup: fix race between policy activation and blkg destruction

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.8high · scored by CNA
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Linux Linux
  • >= 81c1188905f88b77743d1fdeeedfc8cb7b67787d, < b5dae1cd0d8368b4338430ff93403df67f0b8bcc
  • >= bfe46d2efe46c5c952f982e2ca94fe2ec5e58e2a, < 083b58373463a6e5ee60ecb135269348f68ad7df
  • >= f1c006f1c6850c14040f8337753a63119bba39b9, < 17c18a0df70c2b89ff7fcd74622f1540e98d00fd
  • >= f1c006f1c6850c14040f8337753a63119bba39b9, < 91062e3a9ed251726df4e20ff9a1113f1c8ded59
  • >= f1c006f1c6850c14040f8337753a63119bba39b9, < ac34e655dffa74349d885a43d098115336f53842
  • >= f1c006f1c6850c14040f8337753a63119bba39b9, < 2cf9f50a38c1839e549a08e22aa35e8d69e2c8fd
  • >= f1c006f1c6850c14040f8337753a63119bba39b9, < 5313d4d41739b0cb63000747c97bb1217ac45f3e
  • >= 6.1.16, < 6.1.17
  • >= 6.2.3, < 6.2.4

Fixed in b5dae1cd0d8368b4338430ff93403df67f0b8bcc, 083b58373463a6e5ee60ecb135269348f68ad7df, 17c18a0df70c2b89ff7fcd74622f1540e98d00fd, 91062e3a9ed251726df4e20ff9a1113f1c8ded59, ac34e655dffa74349d885a43d098115336f53842, 2cf9f50a38c1839e549a08e22aa35e8d69e2c8fd, 5313d4d41739b0cb63000747c97bb1217ac45f3e, 6.1.17, 6.2.4

Linux Linux
  • 6.3

Fixed in 0, 6.1.17, 6.2.4, 6.6.160, 6.12.114, 6.18.52, 7.2.6, 7.3

Mitigation

Upgrade Linux to b5dae1cd0d8368b4338430ff93403df67f0b8bcc or 083b58373463a6e5ee60ecb135269348f68ad7df or 17c18a0df70c2b89ff7fcd74622f1540e98d00fd or 91062e3a9ed251726df4e20ff9a1113f1c8ded59 or ac34e655dffa74349d885a43d098115336f53842 or 2cf9f50a38c1839e549a08e22aa35e8d69e2c8fd or 5313d4d41739b0cb63000747c97bb1217ac45f3e or 6.1.17 or 6.2.4 or later.

Upgrade Linux to 0 or 6.1.17 or 6.2.4 or 6.6.160 or 6.12.114 or 6.18.52 or 7.2.6 or 7.3 or later.

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published17 Sep 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.