CVE-2026-90325: blk-cgroup: skip dying blkg in blkcg_activate_policy()
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 083b58373463a6e5ee60ecb135269348f68ad7df, 1a267295b1ea6a6477963f3fda84adfecd48fcad, 3d8c3da95c75a4d312e272fc7b4076dd3ba9115c.
Low priority for now. Upgrade to Linux Linux 083b58373463a6e5ee60ecb135269348f68ad7df, 1a267295b1ea6a6477963f3fda84adfecd48fcad, 3d8c3da95c75a4d312e272fc7b4076dd3ba9115c or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 17, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.3affected
- 81c1188905f88b77743d1fdeeedfc8cb7b67787d and later · before b5dae1cd0d8368b4338430ff93403df67f0b8bccaffected · git
- bfe46d2efe46c5c952f982e2ca94fe2ec5e58e2a and later · before 083b58373463a6e5ee60ecb135269348f68ad7dfaffected · git
- f1c006f1c6850c14040f8337753a63119bba39b9 and later · before 1a267295b1ea6a6477963f3fda84adfecd48fcadaffected · git
- f1c006f1c6850c14040f8337753a63119bba39b9 and later · before 7337d012ca3fc3a6a2d1c8e2a19c6d97c38b410daffected · git
- f1c006f1c6850c14040f8337753a63119bba39b9 and later · before 3d8c3da95c75a4d312e272fc7b4076dd3ba9115caffected · git
- f1c006f1c6850c14040f8337753a63119bba39b9 and later · before d8c872901e6459339374e9eea80aa919176c2ccdaffected · git
- f1c006f1c6850c14040f8337753a63119bba39b9 and later · before 5e9220389920f33b6a804d50c548cd0cd1b04634affected · git
- 6.1.16 and later · before 6.1.17affected · semver
- 6.2.3 and later · before 6.2.4affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-90323Sep 17, 2026 · ublk: validate auto buf reg before taking uring_cmd0Monitor
- ← EarlierCVE-2026-90324Sep 17, 2026 · ublk: check import_ubuf() return value31Monitor
- Later →CVE-2026-90326Sep 17, 2026 · blk-cgroup: fix race between policy activation and blkg destruction31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 083b58373463a6e5ee60ecb135269348f68ad7df | Vendor (CNA) |
| Linux Linux | 1a267295b1ea6a6477963f3fda84adfecd48fcad | Vendor (CNA) |
| Linux Linux | 3d8c3da95c75a4d312e272fc7b4076dd3ba9115c | Vendor (CNA) |
| Linux Linux | 5e9220389920f33b6a804d50c548cd0cd1b04634 | Vendor (CNA) |
| Linux Linux | 6.1.17 | Vendor (CNA) |
| Linux Linux | 6.2.4 | Vendor (CNA) |
| Linux Linux | 7337d012ca3fc3a6a2d1c8e2a19c6d97c38b410d | Vendor (CNA) |
| Linux Linux | b5dae1cd0d8368b4338430ff93403df67f0b8bcc | Vendor (CNA) |
| Linux Linux | d8c872901e6459339374e9eea80aa919176c2ccd | Vendor (CNA) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/1a267295b1ea6a6477963f3fda84adfecd48fcad
- git.kernel.org/stable/c/3d8c3da95c75a4d312e272fc7b4076dd3ba9115c
- git.kernel.org/stable/c/5e9220389920f33b6a804d50c548cd0cd1b04634
- git.kernel.org/stable/c/7337d012ca3fc3a6a2d1c8e2a19c6d97c38b410d
- git.kernel.org/stable/c/b5dae1cd0d8368b4338430ff93403df67f0b8bcc
- git.kernel.org/stable/c/d8c872901e6459339374e9eea80aa919176c2ccd
Vendor advisories and official records. Exploit/PoC links are deliberately left out.