{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2026-68467",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2026-68467"
  ],
  "published": "2026-08-15T06:04:33Z",
  "summary": "mtd: mchp23k256: use SPI match data for chip caps",
  "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.",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
    }
  ],
  "affected": [
    {
      "package": {
        "ecosystem": "Raspberry Pi OS:12",
        "name": "linux"
      },
      "versions": [
        "1:6.1.47-1+rpt4"
      ],
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-2712",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v6",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v7",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v7l",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v8",
            "binary_version": "1:6.1.47-1+rpt4"
          }
        ]
      },
      "database_specific": {
        "per_version": {
          "1:6.1.47-1+rpt4": {
            "linux_commit": "655fc658a15ae7a6f37103754adb39ba52a9a14e",
            "upstream_version": "6.1.47",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": "6.1.178",
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-68467"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/2e179b028da9fd628a09286a2c9df4fa076b2cc9"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/a0c38083623c8b210a5b87fd34bebd05aa935ae8"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/7c0a3a73dccc9a3fc701f6be762449f18d0ca0fc"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/dbe2254d1da99c986f9a3392471fc5eaa3229647"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/04ebd3766861f219325852c9598e0f0281cb3636"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/09e044192a42f716215fbd1a100ee87fa57426aa"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/d322e40f4edf92bf0ca329e5aa4ae1c0316feb38"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-08-17T05:50:24Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 7.8,
      "cvss_v3_severity": "High",
      "scenario": "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->size 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."
    }
  }
}