CVE-2026-90325

blk-cgroup: skip dying blkg in blkcg_activate_policy()

HIGH
7.8
CVSS Score
Published: September 17, 2026 at 04:08 PM UTC
Updated: October 19, 2026 at 09:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.1.166.2.36.381c1188905f88b77743d1fdeeedfc8cb7b67787dbfe46d2efe46c5c952f982e2ca94fe2ec5e58e2af1c006f1c6850c14040f8337753a63119bba39b9
Vendor states this is fixed in 083b58373463a6e5ee60ecb135269348f68ad7df (fixed)
Vendor states this is fixed in 1a267295b1ea6a6477963f3fda84adfecd48fcad (fixed)
Vendor states this is fixed in 3d8c3da95c75a4d312e272fc7b4076dd3ba9115c (fixed)
Vendor states this is fixed in 5e9220389920f33b6a804d50c548cd0cd1b04634 (fixed)
Vendor states this is fixed in 7337d012ca3fc3a6a2d1c8e2a19c6d97c38b410d (fixed)
Vendor states this is fixed in b5dae1cd0d8368b4338430ff93403df67f0b8bcc (fixed)
Vendor states this is fixed in d8c872901e6459339374e9eea80aa919176c2ccd (fixed)
Vendor states this is fixed in 6.1.17 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.2.4 (unaffected)
Vendor states this is fixed in 6.3 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card