Vulnerability-Lookup

GHSA-XM4Q-V74W-PX7X

Vulnerability from github – Published: 2026-09-16 12:30 – Updated: 2026-09-16 15:31

Details

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

spi: Fix DMA mapping ownership on partial map failure

If RX mapping fails after TX mapping succeeds, __spi_map_msg() unmaps TX but leaves tx_sg_mapped set. If TX mapping fails on a later transfer, mappings created for earlier transfers remain active.

In both cases, cur_{tx,rx}_dma_dev have not yet been updated because they are assigned only after every transfer has been mapped. The subsequent spi_unmap_msg() may therefore unmap the TX mapping again or release earlier mappings using a NULL or stale device. Using a NULL device can trigger an oops. An empty SG table does not prevent the NULL dereference because dma_unmap_sg_attrs() accesses the device before checking the entry count.

Publish both mapping devices before mapping starts and unwind all failures through __spi_unmap_msg(). This clears the mapping flags and releases each mapping once with the device that created it.

Publishing the devices before the loop also refreshes them when no transfer needs mapping. No mapping flag is set in that case, so current users do not use the pointers as mapping owners.

Severity

9.8 (Critical)


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

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-90012"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-09-16T11:17:13Z",
    "severity": "CRITICAL"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nspi: Fix DMA mapping ownership on partial map failure\n\nIf RX mapping fails after TX mapping succeeds, __spi_map_msg() unmaps\nTX but leaves tx_sg_mapped set. If TX mapping fails on a later\ntransfer, mappings created for earlier transfers remain active.\n\nIn both cases, cur_{tx,rx}_dma_dev have not yet been updated because they\nare assigned only after every transfer has been mapped. The subsequent\nspi_unmap_msg() may therefore unmap the TX mapping again or release\nearlier mappings using a NULL or stale device. Using a NULL device can\ntrigger an oops. An empty SG table does not prevent the NULL dereference\nbecause dma_unmap_sg_attrs() accesses the device before checking the\nentry count.\n\nPublish both mapping devices before mapping starts and unwind all\nfailures through __spi_unmap_msg(). This clears the mapping flags and\nreleases each mapping once with the device that created it.\n\nPublishing the devices before the loop also refreshes them when no\ntransfer needs mapping. No mapping flag is set in that case, so current\nusers do not use the pointers as mapping owners.",
  "id": "GHSA-xm4q-v74w-px7x",
  "modified": "2026-09-16T15:31:06Z",
  "published": "2026-09-16T12:30:45Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-90012"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/367cea239fc93094e5c16a72724800e0358f5c46"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/5def8b6aaad44603740786262b95b6f77df52a1c"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/a38051fa2ddedbc8ec15292c55e276880ec5b9a4"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/cc8354213ad6bd5fb8cc05a3fa3701188d086626"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}

CVE-2026-90012 (GCVE-0-2026-90012)

Vulnerability from cvelistv5 – Published: 2026-09-16 10:33 – Updated: 2026-10-19 08:56

Title

spi: Fix DMA mapping ownership on partial map failure

Summary

In the Linux kernel, the following vulnerability has been resolved: spi: Fix DMA mapping ownership on partial map failure If RX mapping fails after TX mapping succeeds, __spi_map_msg() unmaps TX but leaves tx_sg_mapped set. If TX mapping fails on a later transfer, mappings created for earlier transfers remain active. In both cases, cur_{tx,rx}_dma_dev have not yet been updated because they are assigned only after every transfer has been mapped. The subsequent spi_unmap_msg() may therefore unmap the TX mapping again or release earlier mappings using a NULL or stale device. Using a NULL device can trigger an oops. An empty SG table does not prevent the NULL dereference because dma_unmap_sg_attrs() accesses the device before checking the entry count. Publish both mapping devices before mapping starts and unwind all failures through __spi_unmap_msg(). This clears the mapping flags and releases each mapping once with the device that created it. Publishing the devices before the loop also refreshes them when no transfer needs mapping. No mapping flag is set in that case, so current users do not use the pointers as mapping owners.

Severity

9.8 (Critical)


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

Assigner

Linux CNA under the mitre root

CNA scorecard D 53/100 over 6640 records in the last 180 days details

References

4 references

URL	Tags
https://git.kernel.org/stable/c/cc8354213ad6bd5fb…
https://git.kernel.org/stable/c/a38051fa2ddedbc8e…
https://git.kernel.org/stable/c/5def8b6aaad446037…
https://git.kernel.org/stable/c/367cea239fc93094e…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: e289df82344fecc104ad8326b9ab6da612b9c899 , < cc8354213ad6bd5fb8cc05a3fa3701188d086626 (git) Affected: e289df82344fecc104ad8326b9ab6da612b9c899 , < a38051fa2ddedbc8ec15292c55e276880ec5b9a4 (git) Affected: e289df82344fecc104ad8326b9ab6da612b9c899 , < 5def8b6aaad44603740786262b95b6f77df52a1c (git) Affected: e289df82344fecc104ad8326b9ab6da612b9c899 , < 367cea239fc93094e5c16a72724800e0358f5c46 (git)
Linux	Linux	Affected: 6.11 Unaffected: 0 , < 6.11 (semver) Unaffected: 6.12.110 , ≤ 6.12.* (semver) Unaffected: 6.18.51 , ≤ 6.18.* (semver) Unaffected: 7.2.5 , ≤ 7.2.* (semver) Unaffected: 7.3 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/spi/spi.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "cc8354213ad6bd5fb8cc05a3fa3701188d086626",
              "status": "affected",
              "version": "e289df82344fecc104ad8326b9ab6da612b9c899",
              "versionType": "git"
            },
            {
              "lessThan": "a38051fa2ddedbc8ec15292c55e276880ec5b9a4",
              "status": "affected",
              "version": "e289df82344fecc104ad8326b9ab6da612b9c899",
              "versionType": "git"
            },
            {
              "lessThan": "5def8b6aaad44603740786262b95b6f77df52a1c",
              "status": "affected",
              "version": "e289df82344fecc104ad8326b9ab6da612b9c899",
              "versionType": "git"
            },
            {
              "lessThan": "367cea239fc93094e5c16a72724800e0358f5c46",
              "status": "affected",
              "version": "e289df82344fecc104ad8326b9ab6da612b9c899",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/spi/spi.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.11"
            },
            {
              "lessThan": "6.11",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.110",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.51",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.5",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.110",
                  "versionStartIncluding": "6.11",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.51",
                  "versionStartIncluding": "6.11",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2.5",
                  "versionStartIncluding": "6.11",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.3",
                  "versionStartIncluding": "6.11",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nspi: Fix DMA mapping ownership on partial map failure\n\nIf RX mapping fails after TX mapping succeeds, __spi_map_msg() unmaps\nTX but leaves tx_sg_mapped set. If TX mapping fails on a later\ntransfer, mappings created for earlier transfers remain active.\n\nIn both cases, cur_{tx,rx}_dma_dev have not yet been updated because they\nare assigned only after every transfer has been mapped. The subsequent\nspi_unmap_msg() may therefore unmap the TX mapping again or release\nearlier mappings using a NULL or stale device. Using a NULL device can\ntrigger an oops. An empty SG table does not prevent the NULL dereference\nbecause dma_unmap_sg_attrs() accesses the device before checking the\nentry count.\n\nPublish both mapping devices before mapping starts and unwind all\nfailures through __spi_unmap_msg(). This clears the mapping flags and\nreleases each mapping once with the device that created it.\n\nPublishing the devices before the loop also refreshes them when no\ntransfer needs mapping. No mapping flag is set in that case, so current\nusers do not use the pointers as mapping owners."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 9.8,
            "baseSeverity": "CRITICAL",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:N - Unauthenticated frames to a network-facing SPI NIC such as ENC28J60 or W5500 cause the driver to call spi_sync() with a multi-transfer command-plus-payload message, which reaches __spi_map_msg() in the SPI core with no local login.\nAC:L - The attacker decides when transfers run (packet flood) and can force a partial DMA map failure via memory or IOMMU pressure; controllers such as fsl-lpspi DMA-map even tiny transfers and MUST_TX/MUST_RX dummy buffers create the TX-then-RX failure the bug requires, with no race to win.\nPR:N - The SPI Ethernet receive and transmit paths run before any protocol authentication and have no capability, device-node, or namespace check, so a remote sender needs no privileges.\nUI:N - Once the SPI NIC is configured and up, attacker traffic alone drives spi_sync() into the mapping path; no separate victim action is required.\nS:U - Wrong-device or double DMA unmap and the resulting oops stay inside the host kernel DMA/IOMMU authority and do not cross a VM, guest, or other authorization boundary.\nC:H - On partial map failure the core leaves tx_sg_mapped set after unmapping TX, or leaves earlier live mappings active, then spi_unmap_msg() unmaps again with a NULL or stale DMA device, corrupting IOMMU bookkeeping in a way that can expose kernel memory.\nI:H - Double-unmap or wrong-device unmap of scatter-gather DMA mappings can alias or tear down IOVAs and allow writes into unintended kernel memory, so integrity impact is high under the required higher-severity rule.\nA:H - dma_unmap_sg_attrs() loads the mapping device before checking the SG entry count, so a NULL cur_{tx,rx}_dma_dev (or a NULL sgl on the IOMMU unmap path) causes a repeatable kernel oops."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-10-19T08:56:26.039Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/cc8354213ad6bd5fb8cc05a3fa3701188d086626"
        },
        {
          "url": "https://git.kernel.org/stable/c/a38051fa2ddedbc8ec15292c55e276880ec5b9a4"
        },
        {
          "url": "https://git.kernel.org/stable/c/5def8b6aaad44603740786262b95b6f77df52a1c"
        },
        {
          "url": "https://git.kernel.org/stable/c/367cea239fc93094e5c16a72724800e0358f5c46"
        }
      ],
      "title": "spi: Fix DMA mapping ownership on partial map failure",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-90012",
    "datePublished": "2026-09-16T10:33:19.463Z",
    "dateReserved": "2026-09-11T19:38:34.781Z",
    "dateUpdated": "2026-10-19T08:56:26.039Z",
    "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.

Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

Order JSON

How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Publication & reservation Sightings KEV catalogs Other timestamps

Loading timeline…

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