{
  "id": "CVE-2026-99164",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-99164",
  "published_at": "2026-10-28T10:35:16.694Z",
  "title": "spi: imx: fix slab corruption from undersized DMA bounce buffers",
  "vendor": "Linux",
  "product": "Linux",
  "cvss": {
    "score": 7.8,
    "source": "cna",
    "vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "description": "In the Linux kernel, the following vulnerability has been resolved:\n\nspi: imx: fix slab corruption from undersized DMA bounce buffers\n\nSince commit faa8e404ad8e (\"spi: imx: support dynamic burst length for\nECSPI DMA mode\"), the driver allocates its private DMA TX/RX buffers\nwith kzalloc(dma_len), where dma_len is only rounded up to 4 bytes, but\nmaps, syncs and unmaps them with DMA_CACHE_ALIGNED_LEN(dma_len), i.e.\nrounded up to the cache line size. As a result, the DMA API operates on\nmemory beyond the end of the allocation.\n\nThis was observed on a custom i.MX8MP platform with an mcp251xfd CAN\ncontroller under heavy RPMSG load, as a series of refcount_t warnings\ntriggered from rpmsg_recv_done() in virtio_rpmsg_bus:\n\n  refcount_t: addition on 0; use-after-free.\n  refcount_t: underflow; use-after-free.\n  refcount_t: saturated; leaking memory.\n\nLeading finally to an \"Unable to handle kernel paging request\" oops.\nReproducing this problem took between 30 minutes and roughly 30 hours\nunder the same workload.\n\nHardware watchpoints on the refcount of a struct rpmsg_endpoint showed\nit was overwritten from 2 to 1 by __pi_memcpy_generic() in the\nirq/155-spi2.0 thread. Additionally it was found that a \"normal\"\nrpmsg_recv_done() took 11µs +/-2µs from its kref_get to kref_put. In\nthe error case the same sequence took about 215µs +/-10µs. Based on\nthis, an LLM was used to identify the size mismatch fixed here.\n\nAllocate the buffers with DMA_CACHE_ALIGNED_LEN(dma_len) so they cover\nthe full mapped length, and use the same length for\ndma_sync_single_for_cpu() to stay consistent with map and unmap.\n\nWith this patch applied, the same workload ran for more than 200 hours\nwithout the problem reproducing.",
  "cvss_by_source": {
    "cna": 7.8
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "\u003e= faa8e404ad8e686cb98c51dc507fdcacfb8020ce, \u003c 2777f6637da02da84c9c1ff92f413ce0f0995084",
          "\u003e= faa8e404ad8e686cb98c51dc507fdcacfb8020ce, \u003c 59eb22641f0c526dd064390b11cff99ae87c2858"
        ],
        "fixed_in": [
          "2777f6637da02da84c9c1ff92f413ce0f0995084",
          "59eb22641f0c526dd064390b11cff99ae87c2858"
        ]
      },
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "7.0"
        ],
        "fixed_in": [
          "0",
          "7.2.13",
          "7.3"
        ]
      }
    ],
    "upgrade": [
      "Upgrade Linux to 2777f6637da02da84c9c1ff92f413ce0f0995084 or 59eb22641f0c526dd064390b11cff99ae87c2858 or later.",
      "Upgrade Linux to 0 or 7.2.13 or 7.3 or later."
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
