Kernel use-after-free via blk-cgroup deletion race
Published Sep 17, 2026 · Updated Sep 18, 2026
Use-after-free in affected Linux kernel versions allows local users to trigger invalid kernel memory access while switching I/O schedulers. In block/blk-cgroup.c, blkcg_activate_policy() can take a reference to a blkg after concurrent deletion has unhashed and freed its policy data, causing a second RCU release. Reachability requires permission to change a block device's scheduler and concurrent blkcg deletion; the published record establishes the use-after-free but no further consequence.
Summary
What happened
Use-after-free in affected Linux kernel versions allows local users to trigger invalid kernel memory access while switching I/O schedulers. In block/blk-cgroup.c, blkcg_activate_policy() can take a reference to a blkg after concurrent deletion has unhashed and freed its policy data, causing a second RCU release. Reachability requires permission to change a block device's scheduler and concurrent blkcg deletion; the published record establishes the use-after-free but no further consequence.
The record
- CVE
- CVE-2026-90325
- Published
- Sep 17, 2026
- Updated
- Sep 18, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.1.16 <6.1.17
- Affected versionversion=6.2.3 <6.2.4
- Affected versionversion=6.3
- Affected versionversion=81c1188905f88b77743d1fdeeedfc8cb7b67787d <b5dae1cd0d8368b4338430ff93403df67f0b8bcc
- Affected versionversion=bfe46d2efe46c5c952f982e2ca94fe2ec5e58e2a <083b58373463a6e5ee60ecb135269348f68ad7df
- Affected versionversion=f1c006f1c6850c14040f8337753a63119bba39b9 <1a267295b1ea6a6477963f3fda84adfecd48fcad
- Affected versionversion=f1c006f1c6850c14040f8337753a63119bba39b9 <3d8c3da95c75a4d312e272fc7b4076dd3ba9115c
- Affected versionversion=f1c006f1c6850c14040f8337753a63119bba39b9 <5e9220389920f33b6a804d50c548cd0cd1b04634
- Affected versionversion=f1c006f1c6850c14040f8337753a63119bba39b9 <7337d012ca3fc3a6a2d1c8e2a19c6d97c38b410d
- Affected versionversion=f1c006f1c6850c14040f8337753a63119bba39b9 <d8c872901e6459339374e9eea80aa919176c2ccd
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started