PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-64149 Linux CVE debrief

A Linux kernel vulnerability, CVE-2026-64149, was resolved by moving the dma_map_resource() sanity check into debug code to prevent false positives for MMIO regions. The check was using pfn_valid(), which does not ensure that a PFN is backed by RAM, causing a WARNING on Raspberry Pi 4 during spi_bcm2835 probe. This change affects users of Linux kernel, particularly those using ARM64 with SPARSEMEM and Raspberry Pi 4. The vulnerability has a medium defensive priority.

Vendor
Linux
Product
Unknown
CVSS
MEDIUM 5.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-07-19
Original CVE updated
2026-08-17
Advisory published
2026-07-19
Advisory updated
2026-08-17

Who should care

Users of Linux kernel, particularly those using ARM64 with SPARSEMEM and Raspberry Pi 4, should be aware of this vulnerability and ensure they apply the necessary patches. This includes operators, platform administrators, vulnerability management teams, and security teams who need to review the affected scope and severity.

Technical summary

The dma_map_resource() function in the Linux kernel was using pfn_valid() to check if a range is not RAM. However, pfn_valid() only checks for the availability of the memory map for a PFN, not that it's backed by RAM. This caused false positives for MMIO regions sharing a section with RAM on ARM64 with SPARSEMEM, leading to a WARNING on Raspberry Pi 4. The fix moves the sanity check into debug_dma_map_phys() and uses pfn_valid() && !PageReserved() to correctly identify usable RAM.

Defensive priority

Medium

Recommended defensive actions

  • Apply the kernel patch moving dma_map_resource() sanity check into debug code
  • Use dma-debug filtering to integrate with err_printk()
  • Verify and update Linux kernel to the latest version
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record was published on 2026-07-19T16:17:56.860Z and has not been modified since then. The NVD entry is currently Received. There is limited information available about the vulnerability, and defenders should verify the affected scope and severity with the official advisory. The Linux kernel vulnerability, CVE-2026-64149, was resolved by moving the dma_map_resource() sanity check into debug code to prevent false positives for MMIO regions. Users should review the official advisory for more details.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-64149 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-64149

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-64149 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-64149

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/004a777879ff629f6e0ca3d09ad09fa3452bcc4d

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/181e67bc11c5ec5b87c6c512c2078752b23ca8d4

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/af0c3f05866237f7592219bfe05387bc3bfc99b5

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.