CVE-2026-64149: Software Security Vulnerability Vulnerability

MODERATE
Advisory Identifier: GHSA-pxq7-6qx3-6gp9
Share
CVSS 5.5
Published
Advisory Summary

CVE-2026-64149 is a MODERATE (CVSS 5.5) security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-64149 at a Glance

CVE Identifier CVE-2026-64149
GHSA Identifier GHSA-pxq7-6qx3-6gp9
Severity MODERATE
CVSS v3.1 Base Score 5.5
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 5.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2026-64149

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-64149, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

References

NVD — CVE-2026-64149 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-64149
git.kernel.org/stable/c/004a777879... WEB
https://git.kernel.org/stable/c/004a777879ff629f6e0ca3d09ad09fa3452bcc4d
git.kernel.org/stable/c/181e67bc11... WEB
https://git.kernel.org/stable/c/181e67bc11c5ec5b87c6c512c2078752b23ca8d4
git.kernel.org/stable/c/af0c3f0586... WEB
https://git.kernel.org/stable/c/af0c3f05866237f7592219bfe05387bc3bfc99b5

Frequently Asked Questions

What is CVE-2026-64149?
CVE-2026-64149 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-64149?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2026-64149?
CVE-2026-64149 has a CVSS v3.1 base score of 5.5 (MODERATE) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2026-64149?
CVE-2026-64149 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-64149?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-pxq7-6qx3-6gp9",
  "modified" : "2026-08-17T18:31:00Z",
  "published" : "2026-07-19T18:31:53Z",
  "aliases" : [ "CVE-2026-64149" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ndma-mapping: move dma_map_resource() sanity check into debug code\n\ndma_map_resource() uses pfn_valid() to ensure the range is not RAM.\nHowever, pfn_valid() only checks for availability of the memory map for\na PFN but it does not ensure that the PFN is actually backed by RAM. On\nARM64 with SPARSEMEM (128MB section granularity), MMIO addresses that\nshare a section with RAM will falsely trigger the WARN_ON_ONCE and cause\ndma_map_resource() to return DMA_MAPPING_ERROR.\n\nThis causes a WARNING on Raspberry Pi 4 during spi_bcm2835 probe because\nthe SPI FIFO register (0xfe204004) falls in the same sparsemem section\nas the end of RAM (0xf8000000-0xfbffffff), both in section 31\n(0xf8000000-0xffffffff).\n\nMove the sanity check from dma_map_resource() into debug_dma_map_phys()\nand replace the unreliable pfn_valid() with pfn_valid() &&\n!PageReserved(), which correctly identifies actual usable RAM without\nfalse positives for MMIO regions that happen to have struct pages.\n\nSince dma_map_resource() is dma_map_phys(DMA_ATTR_MMIO), the check\napplies equally to both APIs. Any non-reserved page represents kernel\nmemory to a sufficient degree that using DMA_ATTR_MMIO on it is almost\ncertainly wrong and risks breaking coherency on non-coherent platforms.\nZONE_DEVICE pages used for PCI P2P DMA (MEMORY_DEVICE_PCI_P2PDMA) have\nPageReserved set, so they will not trigger a false positive.\n\nThe check no longer blocks the mapping and uses err_printk() to\nintegrate with dma-debug filtering.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-64149"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/004a777879ff629f6e0ca3d09ad09fa3452bcc4d"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/181e67bc11c5ec5b87c6c512c2078752b23ca8d4"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/af0c3f05866237f7592219bfe05387bc3bfc99b5"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "MODERATE",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-07-19T16:17:56Z"
  }
}