{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2026-68466",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2026-68466"
  ],
  "published": "2026-08-15T06:04:33Z",
  "summary": "mtd: rawnand: lpc32xx_slc: fail DMA transfer on completion timeout",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmtd: rawnand: lpc32xx_slc: fail DMA transfer on completion timeout\n\nlpc32xx_xmit_dma() waits for the DMA completion callback but ignores\nwait_for_completion_timeout(). A timed out DMA transfer is therefore\nunmapped and reported as successful to the NAND read/write path.\n\nReturn -ETIMEDOUT when the completion wait expires. Terminate the DMA\nchannel before unmapping the scatterlist so the timed out transfer cannot\ncontinue to access the buffer after the error is returned.",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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-68466"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/307e4f4c1d4e1575b3495ecc6e41aa2adc40f491"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/c367af37ce7238c96c6071337149099467160746"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/623c4d8e740debb4af28981e3d4e209f9d0260a4"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/bd4a622786f92e1f183f7557ab89dd32891cef60"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/8f5c3ee53a5dc1a0f7cfd780485f2c8b5d17f91d"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/cf7258f57d18026b8f77c0e80ff1805e9caf7250"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/cb2031f8b226efbd13735c07b075e5f14ec11f6d"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/17a8ce84964f243c8f89dc7353ac7e8d3137bc74"
    }
  ],
  "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": 8.8,
      "cvss_v3_severity": "High",
      "scenario": "AV:L - The lpc32xx SLC NAND driver is only exercised through local kernel storage entry points\u2014read/write/ioctl on /dev/mtd* or mtdblock, VFS access to flash-backed mounts (UBIFS/JFFS2/squashfs), or in-kernel mtd_read/mtd_write callers\u2014not via any network packet or remote protocol handler.\nAC:L - An attacker with flash access can repeatedly issue MTD or filesystem read/write operations to stress the NAND controller and DMA engine, hunting for completion timeouts; they control I/O timing and can retry without depending on rare victim-only state beyond issuing local storage traffic.\nPR:L - Unprivileged local users on typical LPC32xx embedded systems can reach the vulnerable DMA path by reading executables or files from flash-backed root filesystems or world-readable mtdblock nodes; root-only /dev/mtd access is not required for the read path through lpc32xx_nand_read_page_syndrome.\nUI:N - Exploitation requires only attacker-initiated storage I/O against the NAND-backed device or mounted filesystem; no victim interaction such as plugging media, approving dialogs, or opening attacker-supplied content is needed.\nS:C - On DMA timeout the driver unmaps the scatterlist while in-flight DMA may continue, allowing the NAND DMA engine to access physical pages reused for unrelated kernel objects\u2014crossing the intended DMA buffer security boundary of the driver.\nC:H - Continued DEV_TO_MEM DMA after dma_unmap_sg can write into repurposed physical pages and leak their prior contents upward; falsely reporting success also returns incomplete or attacker-influenced NAND page data, and post-unmap DMA enables arbitrary kernel memory disclosure via controlled page reuse.\nI:H - In-flight DMA after dma_unmap_sg provides a DMA-after-free style write primitive that can corrupt adjacent kernel heap or stack objects, enabling control-flow hijacking and privilege escalation beyond the intended NAND transfer buffer.\nA:H - DMA-after-unmap corruption commonly provokes kernel oops, panic, or hang; falsely successful timed-out writes can also corrupt flash contents or filesystem metadata on industrial LPC32xx appliances, causing sustained denial of service or device bricking."
    }
  }
}