Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 43 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (14 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 5c83746a0cf2831d4b59f5cf99ef5fbf138564e4 – < 710ae187a5d490a894054d17645cf5c83d37dfbf
    • affected 5c83746a0cf2831d4b59f5cf99ef5fbf138564e4 – < 51d162dfb618f6cf3aa5e331c0305e27771ad884
    • affected 5c83746a0cf2831d4b59f5cf99ef5fbf138564e4 – < 8a2494964edac2a13e82441c2bf887548dc3be0b
    • affected 5c83746a0cf2831d4b59f5cf99ef5fbf138564e4 – < 1e1c36b206c659cf94c6755a1d821ed1babd32bc
    • affected 5c83746a0cf2831d4b59f5cf99ef5fbf138564e4 – < 23e4162405c456ce12c772d5882d306135e828ae
    • affected 5c83746a0cf2831d4b59f5cf99ef5fbf138564e4 – < c056f817e4200fb18079d5052c273a22f191ff0a
  • Linux · Linux

    • affected 3.18
    • unaffected < 3.18
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-90150 badge
[![CVE-2026-90150](https://cveledger.app/badge/CVE-2026-90150.svg)](https://cveledger.app/cve/CVE-2026-90150)

Record last updated .