nvmet: use the local P2P device on metadata allocation failure
Summary
| CVE | CVE-2026-98964 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-10-23 13:17:17 UTC |
| Updated | 2026-10-24 14:16:49 UTC |
| 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. |
Risk And Classification
Primary CVSS: v3.1 7.5 HIGH from 416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | Secondary | 7.5 | HIGH | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| 3.1 | CNA | DECLARED | 7.5 | HIGH | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
CVSS v3.1 Breakdown
Attack Vector
NetworkAttack Complexity
LowPrivileges Required
NoneUser Interaction
NoneScope
UnchangedConfidentiality
NoneIntegrity
NoneAvailability
HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected bcd9a0797d73eeff659582f23277e7ab6e5f18f3 3c231142c4f4bb96836469eb276026ec55940093 git | Not specified |
| CNA | Linux | Linux | affected bcd9a0797d73eeff659582f23277e7ab6e5f18f3 32f21607911a1f69c8f0f93a6c28fe6f8490aa98 git | Not specified |
| CNA | Linux | Linux | affected bcd9a0797d73eeff659582f23277e7ab6e5f18f3 ce79a6c5cc1b8054ec8d3eba16adda4a36113438 git | Not specified |
| CNA | Linux | Linux | affected bcd9a0797d73eeff659582f23277e7ab6e5f18f3 73bf0f9579633b531098a475e6e55c9316763aed git | Not specified |
| CNA | Linux | Linux | affected bcd9a0797d73eeff659582f23277e7ab6e5f18f3 4aa9c0f377a4de5e8fddce76b34ee4529639a1ff git | Not specified |
| CNA | Linux | Linux | affected c440cd080761b18a52cac20f2a42e5da1e3995af git | Not specified |
| CNA | Linux | Linux | affected 8a452d62e7cea3c8a2676a3b89a9118755a1a271 git | Not specified |
| CNA | Linux | Linux | affected 5.10.43 5.11 semver | Not specified |
| CNA | Linux | Linux | affected 5.12.10 5.13 semver | Not specified |
| CNA | Linux | Linux | affected 5.13 | Not specified |
| CNA | Linux | Linux | unaffected 5.13 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.160 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.113 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.57 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2.11 7.2.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.3 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/4aa9c0f377a4de5e8fddce76b34ee4529639a1ff | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/32f21607911a1f69c8f0f93a6c28fe6f8490aa98 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/3c231142c4f4bb96836469eb276026ec55940093 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/ce79a6c5cc1b8054ec8d3eba16adda4a36113438 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/73bf0f9579633b531098a475e6e55c9316763aed | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.