# CVE-2026-90150: pnfs/blocklayout: Fix device leaks on parse failure

> A memory leak in the Linux kernel's pnfs/blocklayout module allows attackers to cause denial of service via crafted parse failures.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-102081, BELL-CVE-2026-90150, DEBIAN-CVE-2026-90150, GHSA-qj3f-qfg4-pxhf, UBUNTU-CVE-2026-90150

## What is CVE-2026-90150?

CVE-2026-90150 is a memory corruption vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2026-90150?


## How do I fix CVE-2026-90150?

Apply the vendor's patch.

## Is CVE-2026-90150 being exploited?

There is no known exploitation of CVE-2026-90150 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-90150 and fix it if it is affected.

What it is: CVE-2026-90150 is a memory corruption vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-90150 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-90150/ (Markdown: https://insights.sbomify.com/CVE-2026-90150/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-90150
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-90150
- OSV: https://osv.dev/vulnerability/CVE-2026-90150

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-90150/
Summaries are generated and may contain mistakes; the official description above is the record.