CVE-2026-90188: null_blk: free global tag_set on init error path
Noroxi assessment
Priority: Monitor (action score 0/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.20% (FIRST EPSS).
- Fixed version: Linux Linux 081cf37e8a0e00cd91d6df53172c9d928790a798, 0b2faa330184340d9418ad2c627c2ae881772e33, 2882e1450fa4597811a951196e07553ea134eb31; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
Low priority for now. Upgrade to Linux Linux 081cf37e8a0e00cd91d6df53172c9d928790a798, 0b2faa330184340d9418ad2c627c2ae881772e33, 2882e1450fa4597811a951196e07553ea134eb31; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 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: null_blk: free global tag_set on init error path If shared_tags is enabled, null_setup_tagset() allocates the global tag_set via null_init_global_tag_set(). If device creation later fails, err_dev destroys the default devices and calls unregister_blkdev(), but never frees the global tag_set. Since module init failed, null_exit() is never invoked, so the global tag_set's tags and maps are permanently leaked. Free the global tag_set in err_dev, matching null_exit() which does if (tag_set.ops) blk_mq_free_tag_set(&tag_set).
- Published
- Sep 17, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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
- 4.13affected
- 82f402fefa50f1675bf918bcd009981bd6b30ac8 and later · before 0b2faa330184340d9418ad2c627c2ae881772e33affected · git
- 82f402fefa50f1675bf918bcd009981bd6b30ac8 and later · before 665c94554ff0d5d88caae7f40c16c8e0a3369edaaffected · git
- 82f402fefa50f1675bf918bcd009981bd6b30ac8 and later · before 2882e1450fa4597811a951196e07553ea134eb31affected · git
- 82f402fefa50f1675bf918bcd009981bd6b30ac8 and later · before 2b59484ac1e64dd78dbe8c6140891c6308085a75affected · git
- 82f402fefa50f1675bf918bcd009981bd6b30ac8 and later · before 081cf37e8a0e00cd91d6df53172c9d928790a798affected · git
- 82f402fefa50f1675bf918bcd009981bd6b30ac8 and later · before 5a1c5ff3a49ba93a1fd0b70537e7a0164071760daffected · git
- before 4.13not affected · semver
- 6.1.188 and later · up to and including 6.1.*not affected · semver
- 6.6.157 and later · up to and including 6.6.*not affected · 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 | before 6.1.190-1 | 6.1.190-1 |
| 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-90186Sep 17, 2026 · null_blk: reject per-device queue resize for shared tag set0Monitor
- ← EarlierCVE-2026-90187Sep 17, 2026 · null_blk: free zones array on device power-off0Monitor
- Later →CVE-2026-90189Sep 17, 2026 · null_blk: register configfs subsystem after creating default devices0Monitor
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 | 081cf37e8a0e00cd91d6df53172c9d928790a798 | Vendor (CNA) |
| Linux Linux | 0b2faa330184340d9418ad2c627c2ae881772e33 | Vendor (CNA) |
| Linux Linux | 2882e1450fa4597811a951196e07553ea134eb31 | Vendor (CNA) |
| Linux Linux | 2b59484ac1e64dd78dbe8c6140891c6308085a75 | Vendor (CNA) |
| Linux Linux | 5a1c5ff3a49ba93a1fd0b70537e7a0164071760d | Vendor (CNA) |
| Linux Linux | 665c94554ff0d5d88caae7f40c16c8e0a3369eda | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| 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
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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 (5 more)Show less
- git.kernel.org/stable/c/0b2faa330184340d9418ad2c627c2ae881772e33
- git.kernel.org/stable/c/2882e1450fa4597811a951196e07553ea134eb31
- git.kernel.org/stable/c/2b59484ac1e64dd78dbe8c6140891c6308085a75
- git.kernel.org/stable/c/5a1c5ff3a49ba93a1fd0b70537e7a0164071760d
- git.kernel.org/stable/c/665c94554ff0d5d88caae7f40c16c8e0a3369eda
Vendor advisories and official records. Exploit/PoC links are deliberately left out.