CVE-2026-90325blk-cgroup: skip dying blkg in blkcg_activate_policy()
- 7.8HighCVSS base score
- 0.16%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: blk-cgroup: skip dying blkg in blkcg_activate_policy() When switching IO schedulers on a block device, blkcg_activate_policy() can race with concurrent blkcg deletion, leading to a use-after-free in rcu_accelerate_cbs. T1: T2: blkg_destroy kill(&blkg->refcnt) // blkg->refcnt=1->0 blkg_release // call_rcu(__blkg_release) ... blkg_free_workfn ->pd_free_fn(pd) elv_iosched_store elevator_switch ... iterate blkg list blkg_get(blkg) // blkg->refcnt=0->1 list_del_init(&blkg->q_node) blkg_put(pinned_blkg) // blkg->refcnt=1->0 blkg_release // call_rcu again rcu_accelerate_cbs // uaf Fix this by checking hlist_unhashed(&blkg->blkcg_node) before getting a reference to the blkg. This is the same check used in blkg_destroy() to detect if a blkg has already been destroyed. If the blkg is already unhashed, skip processing it since it's being destroyed.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 32 days later
· 32 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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.16% · top 94% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 81c1188905f88b77743d1fdeeedfc8cb7b67787d – < b5dae1cd0d8368b4338430ff93403df67f0b8bcc
- affected bfe46d2efe46c5c952f982e2ca94fe2ec5e58e2a – < 083b58373463a6e5ee60ecb135269348f68ad7df
- affected f1c006f1c6850c14040f8337753a63119bba39b9 – < 1a267295b1ea6a6477963f3fda84adfecd48fcad
- affected f1c006f1c6850c14040f8337753a63119bba39b9 – < 7337d012ca3fc3a6a2d1c8e2a19c6d97c38b410d
- affected f1c006f1c6850c14040f8337753a63119bba39b9 – < 3d8c3da95c75a4d312e272fc7b4076dd3ba9115c
- affected f1c006f1c6850c14040f8337753a63119bba39b9 – < d8c872901e6459339374e9eea80aa919176c2ccd
- affected f1c006f1c6850c14040f8337753a63119bba39b9 – < 5e9220389920f33b6a804d50c548cd0cd1b04634
- affected 6.1.16 – < 6.1.17
- affected 6.2.3 – < 6.2.4
- affected 6.3
- unaffected < 6.3
- unaffected 6.1.17 – ≤ 6.1.*
- unaffected 6.2.4 – ≤ 6.2.*
- unaffected 6.6.157 – ≤ 6.6.*
- unaffected 6.12.110 – ≤ 6.12.*
- unaffected 6.18.52 – ≤ 6.18.*
- unaffected 7.2.6 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References7
- https://git.kernel.org/stable/c/b5dae1cd0d8368b4338430ff93403df67f0b8bcc (opens in a new tab)
- https://git.kernel.org/stable/c/083b58373463a6e5ee60ecb135269348f68ad7df (opens in a new tab)
- https://git.kernel.org/stable/c/1a267295b1ea6a6477963f3fda84adfecd48fcad (opens in a new tab)
- https://git.kernel.org/stable/c/7337d012ca3fc3a6a2d1c8e2a19c6d97c38b410d (opens in a new tab)
- https://git.kernel.org/stable/c/3d8c3da95c75a4d312e272fc7b4076dd3ba9115c (opens in a new tab)
- https://git.kernel.org/stable/c/d8c872901e6459339374e9eea80aa919176c2ccd (opens in a new tab)
- https://git.kernel.org/stable/c/5e9220389920f33b6a804d50c548cd0cd1b04634 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-81986 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-90325)Record last updated .