Vulnerability-Lookup

GHSA-V74X-XVFC-H3J3

Vulnerability from github – Published: 2026-08-15 06:32 – Updated: 2026-08-17 06:33

Details

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

iommu/dma-iommu: Fix wrong scatterlist length assignment in P2PDMA path

In iommu_dma_map_sg(), when handling PCI P2PDMA cases, the DMA length of the current scatterlist segment s is incorrectly assigned from the head entry sg->length instead of the current entry s->length.

This typo causes all P2PDMA segments in the scatterlist to inherit the length of the first segment, leading to corrupted DMA lengths for multi- segment scatterlists.

Fix this by using s->length instead of sg->length.

Severity

8.8 (High)


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

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-74277"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-08-15T06:22:27Z",
    "severity": "HIGH"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\niommu/dma-iommu: Fix wrong scatterlist length assignment in P2PDMA path\n\nIn iommu_dma_map_sg(), when handling PCI P2PDMA cases, the DMA length\nof the current scatterlist segment `s` is incorrectly assigned from the\nhead entry `sg-\u003elength` instead of the current entry `s-\u003elength`.\n\nThis typo causes all P2PDMA segments in the scatterlist to inherit the\nlength of the first segment, leading to corrupted DMA lengths for multi-\nsegment scatterlists.\n\nFix this by using `s-\u003elength` instead of `sg-\u003elength`.",
  "id": "GHSA-v74x-xvfc-h3j3",
  "modified": "2026-08-17T06:33:35Z",
  "published": "2026-08-15T06:32:27Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-74277"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/8646f00ce021e49f4f05bc1d4060a0c27b25d0e1"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/db50fb87015b955a5a0c155293b2dd40d63a3b9e"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}

CVE-2026-74277 (GCVE-0-2026-74277)

Vulnerability from cvelistv5 – Published: 2026-08-15 05:57 – Updated: 2026-08-17 05:45

Title

iommu/dma-iommu: Fix wrong scatterlist length assignment in P2PDMA path

Summary

In the Linux kernel, the following vulnerability has been resolved: iommu/dma-iommu: Fix wrong scatterlist length assignment in P2PDMA path In iommu_dma_map_sg(), when handling PCI P2PDMA cases, the DMA length of the current scatterlist segment `s` is incorrectly assigned from the head entry `sg->length` instead of the current entry `s->length`. This typo causes all P2PDMA segments in the scatterlist to inherit the length of the first segment, leading to corrupted DMA lengths for multi- segment scatterlists. Fix this by using `s->length` instead of `sg->length`.

Severity

8.8 (High)


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

Assigner

Linux mitre root Scorecard

References

2 references

URL	Tags
https://git.kernel.org/stable/c/8646f00ce021e49f4…
https://git.kernel.org/stable/c/db50fb87015b955a5…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: a25e7962db0d79882c9d32fd2a67a02e79129c0e , < 8646f00ce021e49f4f05bc1d4060a0c27b25d0e1 (git) Affected: a25e7962db0d79882c9d32fd2a67a02e79129c0e , < db50fb87015b955a5a0c155293b2dd40d63a3b9e (git)
Linux	Linux	Affected: 6.16 Unaffected: 0 , < 6.16 (semver) Unaffected: 7.1.5 , ≤ 7.1.* (semver) Unaffected: 7.2 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/iommu/dma-iommu.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "8646f00ce021e49f4f05bc1d4060a0c27b25d0e1",
              "status": "affected",
              "version": "a25e7962db0d79882c9d32fd2a67a02e79129c0e",
              "versionType": "git"
            },
            {
              "lessThan": "db50fb87015b955a5a0c155293b2dd40d63a3b9e",
              "status": "affected",
              "version": "a25e7962db0d79882c9d32fd2a67a02e79129c0e",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/iommu/dma-iommu.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.16"
            },
            {
              "lessThan": "6.16",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.1.*",
              "status": "unaffected",
              "version": "7.1.5",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.2",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.1.5",
                  "versionStartIncluding": "6.16",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2",
                  "versionStartIncluding": "6.16",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\niommu/dma-iommu: Fix wrong scatterlist length assignment in P2PDMA path\n\nIn iommu_dma_map_sg(), when handling PCI P2PDMA cases, the DMA length\nof the current scatterlist segment `s` is incorrectly assigned from the\nhead entry `sg-\u003elength` instead of the current entry `s-\u003elength`.\n\nThis typo causes all P2PDMA segments in the scatterlist to inherit the\nlength of the first segment, leading to corrupted DMA lengths for multi-\nsegment scatterlists.\n\nFix this by using `s-\u003elength` instead of `sg-\u003elength`."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 8.8,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - Exploitation requires local block/RDMA I/O that reaches dma_map_sg()/ib_dma_map_sg()\u2192iommu_dma_map_sg() with multi-segment PCI P2PDMA scatterlists (e.g., NVMe-RDMA host, apple_nvme) on IOMMU-enabled systems; no direct remote packet handler invokes this mapping path.\nAC:L - An attacker can reliably trigger the bug by crafting I/O sizes and alignments that yield multi-segment scatterlists with differing P2PDMA segment lengths; no uncontrollable heap layout, timing race, or rare victim state is required beyond P2PDMA-capable hardware topology.\nPR:L - Any unprivileged local user with permission to perform I/O on a PCI device engaged in P2PDMA transfers (typical GPU/compute or storage device access) can trigger the corrupted mapping; real root in the init namespace is not required and user namespaces do not grant this capability.\nUI:N - No victim user action is needed beyond the attacker issuing their own read/write or RDMA/block I/O; exploitation does not depend on a separate user opening files, mounting filesystems, or clicking anything.\nS:C - Incorrect sg_dma_len values let PCIe DMA engines perform bus-address transfers beyond the intended buffer, bypassing IOMMU/DMA isolation and allowing a device\u2019s DMA scope to affect host memory outside the mapped region.\nC:H - When the first segment length exceeds a later P2PDMA segment\u2019s true length, inflated DMA metadata causes the device to read past the buffer end over PCI, enabling disclosure of adjacent device or host memory comparable to an out-of-bounds DMA read.\nI:H - Corrupted DMA lengths permit out-of-bounds PCIe DMA writes beyond the allocated P2PDMA buffer, corrupting adjacent memory and providing a memory-corruption primitive that can be leveraged for further compromise of kernel-adjacent data.\nA:H - Out-of-bounds DMA transfers can trigger IOMMU faults, device errors, and kernel oops/panics when hardware accesses unmapped or protected regions, and the corrupted mappings persist until unmap, enabling repeatable disruption."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-17T05:45:18.964Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/8646f00ce021e49f4f05bc1d4060a0c27b25d0e1"
        },
        {
          "url": "https://git.kernel.org/stable/c/db50fb87015b955a5a0c155293b2dd40d63a3b9e"
        }
      ],
      "title": "iommu/dma-iommu: Fix wrong scatterlist length assignment in P2PDMA path",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-74277",
    "datePublished": "2026-08-15T05:57:48.814Z",
    "dateReserved": "2026-08-15T05:44:03.880Z",
    "dateUpdated": "2026-08-17T05:45:18.964Z",
    "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.

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-V74X-XVFC-H3J3

CVE-2026-74277 (GCVE-0-2026-74277)

Tags

Sightings

Nomenclature

Related by attack behaviour