Vulnerability-Lookup

GHSA-VRP7-59VV-QGVC

Vulnerability from github – Published: 2026-07-19 18:31 – Updated: 2026-07-20 15:31

Details

In the Linux kernel, the following vulnerability has been resolved:

nvme-pci: fix dma_vecs leak on p2p memory

We don't unmap P2P memory, so we don't need to track it. The dma_vec allocation was getting leaked on the completion.

Severity

7.5 (High)


                  
                    CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-64020"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-07-19T16:17:42Z",
    "severity": "HIGH"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnvme-pci: fix dma_vecs leak on p2p memory\n\nWe don\u0027t unmap P2P memory, so we don\u0027t need to track it. The dma_vec\nallocation was getting leaked on the completion.",
  "id": "GHSA-vrp7-59vv-qgvc",
  "modified": "2026-07-20T15:31:55Z",
  "published": "2026-07-19T18:31:49Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-64020"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/24ea0de233d9ebb5ebd6f6018eaf2084af25e3dd"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/85686c72966c5ee637893f124ddb31a1cace7bee"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ]
}

CVE-2026-64020 (GCVE-0-2026-64020)

Vulnerability from cvelistv5 – Published: 2026-07-19 15:39 – Updated: 2026-08-05 12:38

Title

nvme-pci: fix dma_vecs leak on p2p memory

Summary

In the Linux kernel, the following vulnerability has been resolved: nvme-pci: fix dma_vecs leak on p2p memory We don't unmap P2P memory, so we don't need to track it. The dma_vec allocation was getting leaked on the completion.

Severity

7.5 (High)


                        
                          CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Assigner

Linux mitre root

References

2 references

URL	Tags
https://git.kernel.org/stable/c/24ea0de233d9ebb5e…
https://git.kernel.org/stable/c/85686c72966c5ee63…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: b8b7570a7ec872f2a27b775c4f8710ca8a357adf , < 24ea0de233d9ebb5ebd6f6018eaf2084af25e3dd (git) Affected: b8b7570a7ec872f2a27b775c4f8710ca8a357adf , < 85686c72966c5ee637893f124ddb31a1cace7bee (git)
Linux	Linux	Affected: 6.17 Unaffected: 0 , < 6.17 (semver) Unaffected: 7.0.11 , ≤ 7.0.* (semver) Unaffected: 7.1 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/nvme/host/pci.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "24ea0de233d9ebb5ebd6f6018eaf2084af25e3dd",
              "status": "affected",
              "version": "b8b7570a7ec872f2a27b775c4f8710ca8a357adf",
              "versionType": "git"
            },
            {
              "lessThan": "85686c72966c5ee637893f124ddb31a1cace7bee",
              "status": "affected",
              "version": "b8b7570a7ec872f2a27b775c4f8710ca8a357adf",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/nvme/host/pci.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.17"
            },
            {
              "lessThan": "6.17",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.0.*",
              "status": "unaffected",
              "version": "7.0.11",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.1",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.0.11",
                  "versionStartIncluding": "6.17",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.1",
                  "versionStartIncluding": "6.17",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnvme-pci: fix dma_vecs leak on p2p memory\n\nWe don\u0027t unmap P2P memory, so we don\u0027t need to track it. The dma_vec\nallocation was getting leaked on the completion."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.5,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:N - On NVMe-oF storage servers with p2pmem-enabled namespaces backed by local PCIe NVMe, a remote client can trigger this via nvmet-tcp read/write commands that flow through submit_bio() into nvme-pci P2P PRP setup and completion.\nAC:L - Once the P2P-capable NVMe/IOMMU configuration is present, a single crafted read or write reliably leaks the dma_vecs allocation; no races or special memory layout are required.\nPR:N - Remote exploitation via nvmet-tcp requires no local privileges on the target when in-band authentication is not configured, matching pre-authentication network service guidance for fabric targets.\nUI:N - Exploitation is achieved entirely through NVMe I/O commands and requires no victim interaction beyond the attacker (or their client) initiating storage operations.\nS:U - The vulnerability causes kernel memory leakage and NVMe I/O denial within the same kernel security boundary; it does not cross VM, container, or IOMMU isolation boundaries.\nC:N - This is a kmalloc/mempool leak with no out-of-bounds read, use-after-free, or information disclosure; freed dma_vecs tracking memory is not exposed to the attacker.\nI:N - No memory corruption, arbitrary write, or code execution primitive is created; impact is limited to resource exhaustion and I/O failure.\nA:H - Each triggering completion permanently exhausts the single-element dmavec mempool, causing persistent BLK_STS_RESOURCE failures that deny subsequent P2P and non-IOVA PRP I/O on the affected NVMe controller until reboot."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T12:38:16.638Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/24ea0de233d9ebb5ebd6f6018eaf2084af25e3dd"
        },
        {
          "url": "https://git.kernel.org/stable/c/85686c72966c5ee637893f124ddb31a1cace7bee"
        }
      ],
      "title": "nvme-pci: fix dma_vecs leak on p2p memory",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-64020",
    "datePublished": "2026-07-19T15:39:14.115Z",
    "dateReserved": "2026-07-19T07:54:57.027Z",
    "dateUpdated": "2026-08-05T12:38:16.638Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Detection rules are retrieved from Rulezet.

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.

Action not permitted

GHSA-VRP7-59VV-QGVC

CVE-2026-64020 (GCVE-0-2026-64020)

Tags

Sightings

Nomenclature

Related by attack behaviour