CVE-2026-90150: pnfs/blocklayout: Fix device leaks on parse failure
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.21% (FIRST EPSS).
- Fixed version: Linux Linux 1e1c36b206c659cf94c6755a1d821ed1babd32bc, 23e4162405c456ce12c772d5882d306135e828ae, 51d162dfb618f6cf3aa5e331c0305e27771ad884; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
Low priority for now. Upgrade to Linux Linux 1e1c36b206c659cf94c6755a1d821ed1babd32bc, 23e4162405c456ce12c772d5882d306135e828ae, 51d162dfb618f6cf3aa5e331c0305e27771ad884; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes 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: pnfs/blocklayout: Fix device leaks on parse failure bl_parse_concat() and bl_parse_stripe() allocate a child device array and then parse each child in turn. If parsing a child fails, the failed child is not counted in nr_children and the parent may be left with a children array that bl_free_device() will not release when nr_children is zero. Release the failed child and the already parsed children before returning the error. Also make bl_free_device() release the child array whenever the children pointer is set, so that partially initialised concat or stripe devices are cleaned up correctly. bl_parse_scsi() can also fail after assigning d->bdev_file and dropping the file reference. Clear the pointer after fput() so that an outer cleanup path does not put it again.
- Published
- Sep 17, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.2% · 11th 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
- 3.18affected
- 5c83746a0cf2831d4b59f5cf99ef5fbf138564e4 and later · before 710ae187a5d490a894054d17645cf5c83d37dfbfaffected · git
- 5c83746a0cf2831d4b59f5cf99ef5fbf138564e4 and later · before 51d162dfb618f6cf3aa5e331c0305e27771ad884affected · git
- 5c83746a0cf2831d4b59f5cf99ef5fbf138564e4 and later · before 8a2494964edac2a13e82441c2bf887548dc3be0baffected · git
- 5c83746a0cf2831d4b59f5cf99ef5fbf138564e4 and later · before 1e1c36b206c659cf94c6755a1d821ed1babd32bcaffected · git
- 5c83746a0cf2831d4b59f5cf99ef5fbf138564e4 and later · before 23e4162405c456ce12c772d5882d306135e828aeaffected · git
- 5c83746a0cf2831d4b59f5cf99ef5fbf138564e4 and later · before c056f817e4200fb18079d5052c273a22f191ff0aaffected · git
- before 3.18not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.160 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 | 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 |
| openSUSE:Tumbleweed | kernel-source | before 7.2.8-1.1 | 7.2.8-1.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-90148Sep 17, 2026 · NFSv4: Fix incorrect argument passed to nfs4_delete_lease() in nfs4_add_lease()0Monitor
- ← EarlierCVE-2026-90149Sep 17, 2026 · NFSv4/flexfiles: fix NULL dereference for NFSv4.0 data servers30Monitor
- Later →CVE-2026-90151Sep 17, 2026 · NFSv4: remove callback IDR entry on client allocation failure39Monitor
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 | 1e1c36b206c659cf94c6755a1d821ed1babd32bc | Vendor (CNA) |
| Linux Linux | 23e4162405c456ce12c772d5882d306135e828ae | Vendor (CNA) |
| Linux Linux | 51d162dfb618f6cf3aa5e331c0305e27771ad884 | Vendor (CNA) |
| Linux Linux | 710ae187a5d490a894054d17645cf5c83d37dfbf | Vendor (CNA) |
| Linux Linux | 8a2494964edac2a13e82441c2bf887548dc3be0b | Vendor (CNA) |
| Linux Linux | c056f817e4200fb18079d5052c273a22f191ff0a | 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 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| 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) |
| opensuse:kernel-source | 7.2.8-1.1 · openSUSE:Tumbleweed | 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/23e4162405c456ce12c772d5882d306135e828ae
- git.kernel.org/stable/c/51d162dfb618f6cf3aa5e331c0305e27771ad884
- git.kernel.org/stable/c/710ae187a5d490a894054d17645cf5c83d37dfbf
- git.kernel.org/stable/c/8a2494964edac2a13e82441c2bf887548dc3be0b
- git.kernel.org/stable/c/c056f817e4200fb18079d5052c273a22f191ff0a
Vendor advisories and official records. Exploit/PoC links are deliberately left out.