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-98964nvmet: use the local P2P device on metadata allocation failure

Description

In the Linux kernel, the following vulnerability has been resolved: nvmet: use the local P2P device on metadata allocation failure nvmet_req_alloc_p2pmem_sgls() assigns req->p2p_dev only after the data and metadata SGL allocations succeed. If the data allocation succeeds but the metadata allocation fails, out_free_sg passes req->p2p_dev to pci_p2pmem_free_sgl() before that assignment has taken place. Pass the local p2p_dev argument instead, so cleanup uses the same PCI device as the successful data allocation.

Timeline

  1. ID reserved

    By Linux

  2. · 28 days later

    Published

  3. · 7 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

CVSS scores of CVE-2026-98964, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Received3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.61% · top 50% of all CVEs (19 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected c440cd080761b18a52cac20f2a42e5da1e3995af – < eb72e2eeff559eb1eb07b1d644ce2bc1a16c4a80
    • affected bcd9a0797d73eeff659582f23277e7ab6e5f18f3 – < 48c8b59429d09a7c3598de425acbc2d3f4e6647b
    • affected bcd9a0797d73eeff659582f23277e7ab6e5f18f3 – < e8f24ae4f45efe6861f801c6ebd2789c9016f1bc
    • affected bcd9a0797d73eeff659582f23277e7ab6e5f18f3 – < 3c231142c4f4bb96836469eb276026ec55940093
    • affected bcd9a0797d73eeff659582f23277e7ab6e5f18f3 – < 32f21607911a1f69c8f0f93a6c28fe6f8490aa98
    • affected bcd9a0797d73eeff659582f23277e7ab6e5f18f3 – < ce79a6c5cc1b8054ec8d3eba16adda4a36113438
    • affected bcd9a0797d73eeff659582f23277e7ab6e5f18f3 – < 73bf0f9579633b531098a475e6e55c9316763aed
    • affected bcd9a0797d73eeff659582f23277e7ab6e5f18f3 – < 4aa9c0f377a4de5e8fddce76b34ee4529639a1ff
    • affected 8a452d62e7cea3c8a2676a3b89a9118755a1a271
    • affected 5.10.43 – < 5.10.273
    • affected 5.12.10 – < 5.13
  • Linux · Linux

    • affected 5.13
    • unaffected < 5.13
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.113 – ≤ 6.12.*
    • unaffected 6.18.57 – ≤ 6.18.*
    • unaffected 7.2.11 – ≤ 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-98964 badge
[![CVE-2026-98964](https://cveledger.app/badge/CVE-2026-98964.svg)](https://cveledger.app/cve/CVE-2026-98964)

Record last updated .