Vulnerability-Lookup

GHSA-P34J-XW9F-X58X

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:

mtd: mchp23k256: use SPI match data for chip caps

The driver stores chip capacity information in both the OF match table and the SPI id table. Probe currently uses of_device_get_match_data(), so a non-OF SPI modalias match falls back to mchp23k256_caps even when the SPI id table selected a different part.

Use spi_get_device_match_data() so SPI id-table driver_data is consumed when OF match data is absent. This keeps the existing default fallback while avoiding the wrong MTD geometry for id-table-only matches.

Severity

7.8 (High)


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

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-68467"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-08-15T06:19:46Z",
    "severity": "HIGH"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmtd: mchp23k256: use SPI match data for chip caps\n\nThe driver stores chip capacity information in both the OF match table\nand the SPI id table. Probe currently uses of_device_get_match_data(),\nso a non-OF SPI modalias match falls back to mchp23k256_caps even when\nthe SPI id table selected a different part.\n\nUse spi_get_device_match_data() so SPI id-table driver_data is consumed\nwhen OF match data is absent. This keeps the existing default fallback\nwhile avoiding the wrong MTD geometry for id-table-only matches.",
  "id": "GHSA-p34j-xw9f-x58x",
  "modified": "2026-08-17T06:33:03Z",
  "published": "2026-08-15T06:32:07Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-68467"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/04ebd3766861f219325852c9598e0f0281cb3636"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/09e044192a42f716215fbd1a100ee87fa57426aa"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/2e179b028da9fd628a09286a2c9df4fa076b2cc9"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/7c0a3a73dccc9a3fc701f6be762449f18d0ca0fc"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/a0c38083623c8b210a5b87fd34bebd05aa935ae8"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/d322e40f4edf92bf0ca329e5aa4ae1c0316feb38"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/dbe2254d1da99c986f9a3392471fc5eaa3229647"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}

CVE-2026-68467 (GCVE-0-2026-68467)

Vulnerability from cvelistv5 – Published: 2026-08-15 05:51 – Updated: 2026-08-17 05:39

Title

mtd: mchp23k256: use SPI match data for chip caps

Summary

In the Linux kernel, the following vulnerability has been resolved: mtd: mchp23k256: use SPI match data for chip caps The driver stores chip capacity information in both the OF match table and the SPI id table. Probe currently uses of_device_get_match_data(), so a non-OF SPI modalias match falls back to mchp23k256_caps even when the SPI id table selected a different part. Use spi_get_device_match_data() so SPI id-table driver_data is consumed when OF match data is absent. This keeps the existing default fallback while avoiding the wrong MTD geometry for id-table-only matches.

Severity

7.8 (High)


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

Assigner

Linux mitre root

References

7 references

URL	Tags
https://git.kernel.org/stable/c/2e179b028da9fd628…
https://git.kernel.org/stable/c/a0c38083623c8b210…
https://git.kernel.org/stable/c/7c0a3a73dccc9a3fc…
https://git.kernel.org/stable/c/dbe2254d1da99c986…
https://git.kernel.org/stable/c/04ebd3766861f2193…
https://git.kernel.org/stable/c/09e044192a42f7162…
https://git.kernel.org/stable/c/d322e40f4edf92bf0…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: 4379075a870b8de43a9ecd5b46884953234fc669 , < 2e179b028da9fd628a09286a2c9df4fa076b2cc9 (git) Affected: 4379075a870b8de43a9ecd5b46884953234fc669 , < a0c38083623c8b210a5b87fd34bebd05aa935ae8 (git) Affected: 4379075a870b8de43a9ecd5b46884953234fc669 , < 7c0a3a73dccc9a3fc701f6be762449f18d0ca0fc (git) Affected: 4379075a870b8de43a9ecd5b46884953234fc669 , < dbe2254d1da99c986f9a3392471fc5eaa3229647 (git) Affected: 4379075a870b8de43a9ecd5b46884953234fc669 , < 04ebd3766861f219325852c9598e0f0281cb3636 (git) Affected: 4379075a870b8de43a9ecd5b46884953234fc669 , < 09e044192a42f716215fbd1a100ee87fa57426aa (git) Affected: 4379075a870b8de43a9ecd5b46884953234fc669 , < d322e40f4edf92bf0ca329e5aa4ae1c0316feb38 (git)
Linux	Linux	Affected: 4.13 Unaffected: 0 , < 4.13 (semver) Unaffected: 5.15.212 , ≤ 5.15.* (semver) Unaffected: 6.1.178 , ≤ 6.1.* (semver) Unaffected: 6.6.145 , ≤ 6.6.* (semver) Unaffected: 6.12.97 , ≤ 6.12.* (semver) Unaffected: 6.18.40 , ≤ 6.18.* (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/mtd/devices/mchp23k256.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "2e179b028da9fd628a09286a2c9df4fa076b2cc9",
              "status": "affected",
              "version": "4379075a870b8de43a9ecd5b46884953234fc669",
              "versionType": "git"
            },
            {
              "lessThan": "a0c38083623c8b210a5b87fd34bebd05aa935ae8",
              "status": "affected",
              "version": "4379075a870b8de43a9ecd5b46884953234fc669",
              "versionType": "git"
            },
            {
              "lessThan": "7c0a3a73dccc9a3fc701f6be762449f18d0ca0fc",
              "status": "affected",
              "version": "4379075a870b8de43a9ecd5b46884953234fc669",
              "versionType": "git"
            },
            {
              "lessThan": "dbe2254d1da99c986f9a3392471fc5eaa3229647",
              "status": "affected",
              "version": "4379075a870b8de43a9ecd5b46884953234fc669",
              "versionType": "git"
            },
            {
              "lessThan": "04ebd3766861f219325852c9598e0f0281cb3636",
              "status": "affected",
              "version": "4379075a870b8de43a9ecd5b46884953234fc669",
              "versionType": "git"
            },
            {
              "lessThan": "09e044192a42f716215fbd1a100ee87fa57426aa",
              "status": "affected",
              "version": "4379075a870b8de43a9ecd5b46884953234fc669",
              "versionType": "git"
            },
            {
              "lessThan": "d322e40f4edf92bf0ca329e5aa4ae1c0316feb38",
              "status": "affected",
              "version": "4379075a870b8de43a9ecd5b46884953234fc669",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/mtd/devices/mchp23k256.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "4.13"
            },
            {
              "lessThan": "4.13",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.15.*",
              "status": "unaffected",
              "version": "5.15.212",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.1.*",
              "status": "unaffected",
              "version": "6.1.178",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.145",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.97",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.40",
              "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": "5.15.212",
                  "versionStartIncluding": "4.13",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.1.178",
                  "versionStartIncluding": "4.13",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.6.145",
                  "versionStartIncluding": "4.13",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.97",
                  "versionStartIncluding": "4.13",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.40",
                  "versionStartIncluding": "4.13",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.1.5",
                  "versionStartIncluding": "4.13",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2",
                  "versionStartIncluding": "4.13",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmtd: mchp23k256: use SPI match data for chip caps\n\nThe driver stores chip capacity information in both the OF match table\nand the SPI id table. Probe currently uses of_device_get_match_data(),\nso a non-OF SPI modalias match falls back to mchp23k256_caps even when\nthe SPI id table selected a different part.\n\nUse spi_get_device_match_data() so SPI id-table driver_data is consumed\nwhen OF match data is absent. This keeps the existing default fallback\nwhile avoiding the wrong MTD geometry for id-table-only matches."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.8,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - The flaw is exercised only through local MTD I/O (mtdchar read/write or MEMREAD/MEMWRITE ioctls on /dev/mtdN) after probe; mchp23k256 is an on-board SPI SRAM driver with no network, Bluetooth, or remote-protocol entry point.\nAC:L - On affected deployments (mchp23lcv1024 matched via SPI id table without OF), every mtd read/write deterministically uses 2-byte addresses on a 3-byte/128K part; the attacker chooses offsets and lengths to mis-map logical MTD access across the chip with no race or uncontrollable memory layout.\nPR:L - The path from mtdchar_open through mchp23k256_read/write performs no capability checks beyond device-node permissions; on embedded/industrial boards where SPI SRAM MTD nodes are group- or world-accessible, a local unprivileged user can trigger the defective addressing.\nUI:N - No victim interaction is required beyond the attacker issuing their own mtd reads or writes; probe misconfiguration is automatic at boot and persists for all subsequent transfers.\nS:U - Impact is confined to incorrect SPI SRAM access within the same kernel/host security authority; there is no VM escape, IOMMU bypass, or cross-sandbox boundary crossing.\nC:H - Wrong addr_width makes SPI reads return data from unintended chip offsets while mtdchar still caps logical size at 32K, enabling out-of-bounds disclosure of up to ~96K of 128K SRAM contents (credentials, runtime state) outside the reported geometry.\nI:H - Mis-encoded write addresses cause out-of-bounds stores into the full 128K device despite mtd-\u003esize enforcing a 32K bound, corrupting SRAM regions the attacker should not be able to reach through the MTD interface.\nA:H - Desynchronized SPI transactions from address-width mismatch can stall spi_sync() and hang the bus, and corrupted on-board SRAM can crash safety-critical embedded services or trigger watchdog resets on industrial controllers."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-17T05:39:11.779Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/2e179b028da9fd628a09286a2c9df4fa076b2cc9"
        },
        {
          "url": "https://git.kernel.org/stable/c/a0c38083623c8b210a5b87fd34bebd05aa935ae8"
        },
        {
          "url": "https://git.kernel.org/stable/c/7c0a3a73dccc9a3fc701f6be762449f18d0ca0fc"
        },
        {
          "url": "https://git.kernel.org/stable/c/dbe2254d1da99c986f9a3392471fc5eaa3229647"
        },
        {
          "url": "https://git.kernel.org/stable/c/04ebd3766861f219325852c9598e0f0281cb3636"
        },
        {
          "url": "https://git.kernel.org/stable/c/09e044192a42f716215fbd1a100ee87fa57426aa"
        },
        {
          "url": "https://git.kernel.org/stable/c/d322e40f4edf92bf0ca329e5aa4ae1c0316feb38"
        }
      ],
      "title": "mtd: mchp23k256: use SPI match data for chip caps",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-68467",
    "datePublished": "2026-08-15T05:51:25.949Z",
    "dateReserved": "2026-07-30T09:28:09.396Z",
    "dateUpdated": "2026-08-17T05:39:11.779Z",
    "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.