# CVE-2026-64149: linux: In the Linux kernel, the following vulnerability has been resolved:  dma-mapping: move dma_map_resource() sanity chec...

CVE-2026-64149 is fixed in 20 products on 1 platform, first by ALAS2023-2026-1881, released June 22, 2026. It is not reported as exploited. Patch Radar priority: Routine.

- Web page: https://patchblox.com/security/cve/CVE-2026-64149
- Priority: Routine
- CVSS: 5.5 (medium)
- EPSS: 0.0016
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Jun 22, 2026

## Description

In the Linux kernel, the following vulnerability has been resolved:  dma-mapping: move dma_map_resource() sanity check into debug code  dma_map_resource() uses pfn_valid() to ensure the range is not RAM. However, pfn_valid() only checks for availability of the memory map for a PFN but it does not ensure that the PFN is actually backed by RAM. On ARM64 with SPARSEMEM (128MB section granularity), MMIO addresses that share a section with RAM will falsely trigger the WARN_ON_ONCE and cause dma_map_resource() to return DMA_MAPPING_ERROR.  This causes a WARNING on Raspberry Pi 4 during spi_bcm2835 probe because the SPI FIFO register (0xfe204004) falls in the same sparsemem section as the end of RAM (0xf8000000-0xfbffffff), both in section 31 (0xf8000000-0xffffffff).  Move the sanity check from dma_map_resource() into debug_dma_map_phys() and replace the unreliable pfn_valid() with pfn_valid() && !PageReserved(), which correctly identifies actual usable RAM without false positives for MMIO regions that happen to have struct pages.  Since dma_map_resource() is dma_map_phys(DMA_ATTR_MMIO), the check applies equally to both APIs. Any non-reserved page represents kernel memory to a sufficient degree that using DMA_ATTR_MMIO on it is almost certainly wrong and risks breaking coherency on non-coherent platforms. ZONE_DEVICE pages used for PCI P2P DMA (MEMORY_DEVICE_PCI_P2PDMA) have PageReserved set, so they will not trigger a false positive.  The check no longer blocks the mapping and uses err_printk() to integrate with dma-debug filtering.

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | bpftool6.18 amzn 2023 | 1:6.18.35-68.127.amzn2023 | [ALAS2023-2026-1881](https://patchblox.com/security/data/fix/linux/alas2023-2026-1881.md) | Jun 22, 2026 |
| Linux | bpftool6.18-debuginfo amzn 2023 | 1:6.18.35-68.127.amzn2023 | [ALAS2023-2026-1881](https://patchblox.com/security/data/fix/linux/alas2023-2026-1881.md) | Jun 22, 2026 |
| Linux | kernel-livepatch-6.18.35-68.127 amzn 2023 | 1:1.0-0.amzn2023 | [ALAS2023-2026-1881](https://patchblox.com/security/data/fix/linux/alas2023-2026-1881.md) | Jun 22, 2026 |
| Linux | kernel6.18 amzn 2023 | 1:6.18.35-68.127.amzn2023 | [ALAS2023-2026-1881](https://patchblox.com/security/data/fix/linux/alas2023-2026-1881.md) | Jun 22, 2026 |
| Linux | kernel6.18-debuginfo amzn 2023 | 1:6.18.35-68.127.amzn2023 | [ALAS2023-2026-1881](https://patchblox.com/security/data/fix/linux/alas2023-2026-1881.md) | Jun 22, 2026 |
| Linux | kernel6.18-debuginfo-common-aarch64 amzn 2023 | 1:6.18.35-68.127.amzn2023 | [ALAS2023-2026-1881](https://patchblox.com/security/data/fix/linux/alas2023-2026-1881.md) | Jun 22, 2026 |
| Linux | kernel6.18-debuginfo-common-x86_64 amzn 2023 | 1:6.18.35-68.127.amzn2023 | [ALAS2023-2026-1881](https://patchblox.com/security/data/fix/linux/alas2023-2026-1881.md) | Jun 22, 2026 |
| Linux | kernel6.18-devel amzn 2023 | 1:6.18.35-68.127.amzn2023 | [ALAS2023-2026-1881](https://patchblox.com/security/data/fix/linux/alas2023-2026-1881.md) | Jun 22, 2026 |
| Linux | kernel6.18-headers amzn 2023 | 1:6.18.35-68.127.amzn2023 | [ALAS2023-2026-1881](https://patchblox.com/security/data/fix/linux/alas2023-2026-1881.md) | Jun 22, 2026 |
| Linux | kernel6.18-modules-extra amzn 2023 | 1:6.18.35-68.127.amzn2023 | [ALAS2023-2026-1881](https://patchblox.com/security/data/fix/linux/alas2023-2026-1881.md) | Jun 22, 2026 |
| Linux | kernel6.18-modules-extra-common amzn 2023 | 1:6.18.35-68.127.amzn2023 | [ALAS2023-2026-1881](https://patchblox.com/security/data/fix/linux/alas2023-2026-1881.md) | Jun 22, 2026 |
| Linux | kernel6.18-tools amzn 2023 | 1:6.18.35-68.127.amzn2023 | [ALAS2023-2026-1881](https://patchblox.com/security/data/fix/linux/alas2023-2026-1881.md) | Jun 22, 2026 |
| Linux | kernel6.18-tools-debuginfo amzn 2023 | 1:6.18.35-68.127.amzn2023 | [ALAS2023-2026-1881](https://patchblox.com/security/data/fix/linux/alas2023-2026-1881.md) | Jun 22, 2026 |
| Linux | kernel6.18-tools-devel amzn 2023 | 1:6.18.35-68.127.amzn2023 | [ALAS2023-2026-1881](https://patchblox.com/security/data/fix/linux/alas2023-2026-1881.md) | Jun 22, 2026 |
| Linux | linux Debian 14 | 7.0.12-1 | [DEBIAN-CVE-2026-64149](https://patchblox.com/security/data/fix/linux/debian-cve-2026-64149.md) | Jul 20, 2026 |
| Linux | microvm-kernel6.18 amzn 2023 | 1:6.18.35-68.127.amzn2023 | [ALAS2023-2026-1881](https://patchblox.com/security/data/fix/linux/alas2023-2026-1881.md) | Jun 22, 2026 |
| Linux | perf6.18 amzn 2023 | 1:6.18.35-68.127.amzn2023 | [ALAS2023-2026-1881](https://patchblox.com/security/data/fix/linux/alas2023-2026-1881.md) | Jun 22, 2026 |
| Linux | perf6.18-debuginfo amzn 2023 | 1:6.18.35-68.127.amzn2023 | [ALAS2023-2026-1881](https://patchblox.com/security/data/fix/linux/alas2023-2026-1881.md) | Jun 22, 2026 |
| Linux | python3-perf6.18 amzn 2023 | 1:6.18.35-68.127.amzn2023 | [ALAS2023-2026-1881](https://patchblox.com/security/data/fix/linux/alas2023-2026-1881.md) | Jun 22, 2026 |
| Linux | python3-perf6.18-debuginfo amzn 2023 | 1:6.18.35-68.127.amzn2023 | [ALAS2023-2026-1881](https://patchblox.com/security/data/fix/linux/alas2023-2026-1881.md) | Jun 22, 2026 |

---

Data as of 2026-11-08T06:59:42Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.
