Back to the CVE list
CVE-2026-98964

nvmet: use the local P2P device on metadata allocation failure

CVSS score

—

EPSS probability

—

Risk score

—

Published

3 h ago

OverviewPublic Exploits (0)NewsroomVulnerability Timeline
Patch status has not yet been verified

Resmî kaynaklarda yeterli kanıt bulunamadı. Bu sonuç “yama yok” anlamına gelmez.

Impact on My Inventory

Only the personal products you have added to your account are assessed; an organisation's inventory does not appear here.

Checking session…

Vulnerability description

DayBreach AI Explanation

Verified against sources

CVE-2026-98964 Linux Kernel nvmet Memory Allocation Vulnerability

Sources read

1

Source agreement

Tam uyum

Evidence confidence

%55

Short explanation

A vulnerability exists in the Linux kernel nvmet subsystem that causes improper P2P device cleanup during a metadata allocation failure.

Why does it matter?

When metadata memory allocation fails, the routine may pass an incorrect PCI P2P device reference to the cleanup handler, leading to instability or unexpected behavior.

What should be done?

  • Monitor and apply relevant kernel updates
  • Ensure the local p2p_dev argument is passed to the cleanup routine
Chain of evidence and sources2 verified claims

nvmet_req_alloc_p2pmem_sgls() fonksiyonu req->p2p_dev atamasını veri ve meta veri SGL tahsisleri başarılı olduktan sonra yapar.

S0 · daybreach-canonicalS1 · cvelist

Meta veri tahsisi başarısız olduğunda out_free_sg, atama yapılmamış req->p2p_dev değerini pci_p2pmem_free_sgl() fonksiyonuna aktarır.

S0 · daybreach-canonicalS1 · cvelist
Show the technical text from the sources

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.

This explanation was compiled automatically from the source records. Scores, active exploitation, patch and exploit status come straight from the sources.

IMPACT: Affected Products and Software

Affected Products

The following products are affected by CVE-2026-98964 vulnerability. Where our threat engine knows the exact affected versions, they are listed below.

IDVENDORPRODUCTACTION
1linuxLinux View
2linuxLinux View
Total affected vendors: 1|Products: 2

RED HAT CSAF/VEX: Product Impact Check

Red Hat has not yet published a CSAF/VEX impact record for this CVE. This does not mean “not affected”.

SCORING: CVSS from Multiple Sources

CVSS Scores

The Common Vulnerability Scoring System is a standardised framework for assessing the severity of vulnerabilities in software and systems. We collect and display CVSS scores from several sources for each CVE.

SCOREVERSIONSEVERITYVECTORSOURCE
The sources have not yet published a verified CVSS metric.

Patch and Remediation Guide

Solution & Remediation Advisory

Patch status unknown

İncelenen resmî kaynaklarda yama durumu doğrulanamadı. Bu sonuç “yama yok” anlamına gelmez.

Confirm the affected product and version against the source evidence above.
Restrict access to internet-facing services and apply network segmentation.
Until a patch is confirmed, follow the vendor advisory; do not read an unknown status as “no patch”.
Monitor server logs and network endpoints for signs of anomalous execution.

Public exploit and active exploitation status

Verified exploit intelligence

No verified public PoC, exploit repository or Metasploit module has been found for this CVE yet.

Weakness Classification and Attack Patterns (CWE & CAPEC)

CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorises the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-98964 is associated with the following CWEs:

CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')CWE-20: Improper Input Validation

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-98964 weaknesses.

CAPEC-66: SQL InjectionCAPEC-126: Path TraversalCAPEC-28: OS Command Injection

Official Sources and Advisories

https://git.kernel.org/stable/c/3c231142c4f4bb96836469eb276026ec55940093vendor-advisoryhttps://git.kernel.org/stable/c/32f21607911a1f69c8f0f93a6c28fe6f8490aa98vendor-advisoryhttps://git.kernel.org/stable/c/ce79a6c5cc1b8054ec8d3eba16adda4a36113438vendor-advisoryhttps://git.kernel.org/stable/c/73bf0f9579633b531098a475e6e55c9316763aedvendor-advisoryhttps://git.kernel.org/stable/c/4aa9c0f377a4de5e8fddce76b34ee4529639a1ffvendor-advisory

Yama durumu bilinmiyor

İncelenen resmî kaynaklarda yama durumu doğrulanamadı. Bu sonuç “yama yok” anlamına gelmez.

Follow the vendor

L
linux logo
linux

Similar Vulnerabilities

Get this vulnerability through the API

Affected products, version ranges, exploitation status and patch information in a single request, with a free key.

Get a free keyDocumentation
curl -H "x-api-key: $DAYBREACH_API_KEY" \
  "https://api.daybreach.dev/api/v1/intel/cves/CVE-2026-98964"
CVE-2026-98964 · nvmet: use the local P2P device on metadata…