← All Advisories
Reported from OT-Advisories.com as of

CVE-2026-90325

Last refreshed2026-10-19

Status: UPDATED  |  Advisory ID: CVE-2026-90325

Key Details

CVECVE-2026-90325
CVSS Score / Version
7.8 (High) / CVSS v3.1
Updated2026-10-19
CVSS Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS Prose
attack vector is local; attack complexity is low; privileges required is low; user interaction is none; scope is unchanged; confidentiality impact is high; integrity impact is high; availability impact is high.
Affected products
Linux Kernel

Affected Products, Subsystems & Sectors

VendorProductAffected VersionsPatch Status
LinuxLinux Kernel
SubsystemsOT Supporting Infrastructure
SectorsAll Sectors

What to Know

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. (NVD)

What to Do

Monitor Linux's web page for any future patch releases.

References

SourceReference
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-90325
CVEhttps://www.cve.org/CVERecord?id=CVE-2026-90325
Report compilation © 2026 OT-Advisories.com  ·  CC BY 4.0  ·  Source materials remain the property of their respective publishers as cited.