Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 34 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-90326, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 81c1188905f88b77743d1fdeeedfc8cb7b67787d – < b5dae1cd0d8368b4338430ff93403df67f0b8bcc
    • affected bfe46d2efe46c5c952f982e2ca94fe2ec5e58e2a – < 083b58373463a6e5ee60ecb135269348f68ad7df
    • affected f1c006f1c6850c14040f8337753a63119bba39b9 – < 17c18a0df70c2b89ff7fcd74622f1540e98d00fd
    • affected f1c006f1c6850c14040f8337753a63119bba39b9 – < 91062e3a9ed251726df4e20ff9a1113f1c8ded59
    • affected f1c006f1c6850c14040f8337753a63119bba39b9 – < ac34e655dffa74349d885a43d098115336f53842
    • affected f1c006f1c6850c14040f8337753a63119bba39b9 – < 2cf9f50a38c1839e549a08e22aa35e8d69e2c8fd
    • affected f1c006f1c6850c14040f8337753a63119bba39b9 – < 5313d4d41739b0cb63000747c97bb1217ac45f3e
    • affected 6.1.16 – < 6.1.17
    • affected 6.2.3 – < 6.2.4
  • Linux · Linux

    • affected 6.3
    • unaffected < 6.3
    • unaffected 6.1.17 – ≤ 6.1.*
    • unaffected 6.2.4 – ≤ 6.2.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-90326 badge
[![CVE-2026-90326](https://cveledger.app/badge/CVE-2026-90326.svg)](https://cveledger.app/cve/CVE-2026-90326)

Record last updated .