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-90411nvme-fc: unmap cmd_iu DMA on rsp_iu mapping failure in init_request

Description

In the Linux kernel, the following vulnerability has been resolved: nvme-fc: unmap cmd_iu DMA on rsp_iu mapping failure in init_request __nvme_fc_init_request() maps cmd_iu and then rsp_iu for DMA. If the rsp_iu mapping fails, the original code only recorded the error and fell through: it left the already-mapped cmd_iu unmapped and still marked the op as FCPOP_STATE_IDLE before returning. Since blk-mq does not call .exit_request() when .init_request() fails, the cmd_iu mapping is leaked for every op whose rsp_iu mapping fails. Jump to an error path on rsp_iu mapping failure that unmaps cmd_iu and returns the error without marking the op idle, so it stays in the FCPOP_STATE_UNINIT state set by the initial memset().

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 32 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 88% of all CVEs (17 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 e399441de9115cd472b8ace6c517708273ca7997 – < c0892cfb60a75e2c86ba8e2127b133f6549c12b3
    • affected e399441de9115cd472b8ace6c517708273ca7997 – < 5e820d04c241c81a47e1940349018690e93d8167
    • affected e399441de9115cd472b8ace6c517708273ca7997 – < bb0251991420c25e3ceeac40ea09250d79ed7ef0
    • affected e399441de9115cd472b8ace6c517708273ca7997 – < acc173608ca7abe5dee8983086b44efd8b0dbc84
    • affected e399441de9115cd472b8ace6c517708273ca7997 – < 18c5781ed8bc2f423c26ec93e47e2057cd76a783
    • affected e399441de9115cd472b8ace6c517708273ca7997 – < bd764baf82bb46e958a0bd0b481630dd71313055
    • affected e399441de9115cd472b8ace6c517708273ca7997 – < be5eb47ee3fea338efae1a5b678d6bb5f0fcc931
    • affected e399441de9115cd472b8ace6c517708273ca7997 – < f49d0c3a8d56a7cda1628ae17341a4a42063563c
  • Linux · Linux

    • affected 4.10
    • unaffected < 4.10
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .