CVE-2026-90201: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-6rvq-r5r4-hcv8
Published
Advisory Summary

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

CVE-2026-90201 at a Glance

CVE Identifier CVE-2026-90201
GHSA Identifier GHSA-6rvq-r5r4-hcv8
Severity N/A
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-90201

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-90201, 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: net: page_pool: fix UAF in __page_pool_release_netmem_dma on xa_cmpxchg race This bug was discovered while testing the hns3 driver under channel reconfiguration (`ethtool -L` / `ethtool -G`) with iperf3 traffic on arm64. The race is intermittently triggered when page_pool_destroy() runs page_pool_scrub() concurrently with page return via page_pool_put_netmem() on a different CPU. A WARN in page_pool_clear_pp_info() surfaced the dangling DMA index bits left by the cmpxchg loser, which led to the investigation. page_pool_scrub() iterates pool->dma_mapped via xa_for_each() with no page ref held. __page_pool_release_netmem_dma() currently reads and writes netmem fields (dma_addr, DMA index bits in pp_magic) after xa_cmpxchg() returns. The unref path calls put_page() unconditionally regardless of the cmpxchg outcome; when it loses the cmpxchg, it still frees the page before the scrub winner finishes these netmem accesses, so scrub touches a freed page -- a Use-After-Free. Fix this by splitting the DMA release into two functions: 1. __page_pool_unmap_netmem_dma() caches dma_addr before xa_cmpxchg(), does the cmpxchg to remove the DMA mapping, and calls dma_unmap on the cached address. It never touches netmem fields after the cmpxchg, making it safe for the scrub path which holds no page ref. 2. __page_pool_release_netmem_dma() wraps the above and additionally clears dma_addr and DMA index bits in netmem fields. This is safe only when the caller holds a page ref, so it is used by the return path (page_pool_return_netmem). The scrub path calls __page_pool_unmap_netmem_dma() directly; the return path calls __page_pool_release_netmem_dma().

References

Frequently Asked Questions

What is CVE-2026-90201?
CVE-2026-90201 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-90201?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-90201?
CVE-2026-90201 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-90201?
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
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-6rvq-r5r4-hcv8",
  "modified" : "2026-09-17T18:31:55Z",
  "published" : "2026-09-17T18:31:55Z",
  "aliases" : [ "CVE-2026-90201" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: page_pool: fix UAF in __page_pool_release_netmem_dma on xa_cmpxchg race\n\nThis bug was discovered while testing the hns3 driver under channel\nreconfiguration (`ethtool -L` / `ethtool -G`) with iperf3 traffic on\narm64. The race is intermittently triggered when page_pool_destroy()\nruns page_pool_scrub() concurrently with page return via\npage_pool_put_netmem() on a different CPU. A WARN in\npage_pool_clear_pp_info() surfaced the dangling DMA index bits left\nby the cmpxchg loser, which led to the investigation.\n\npage_pool_scrub() iterates pool->dma_mapped via xa_for_each() with no\npage ref held. __page_pool_release_netmem_dma() currently reads and\nwrites netmem fields (dma_addr, DMA index bits in pp_magic) after\nxa_cmpxchg() returns. The unref path calls put_page() unconditionally\nregardless of the cmpxchg outcome; when it loses the cmpxchg, it still\nfrees the page before the scrub winner finishes these netmem accesses,\nso scrub touches a freed page -- a Use-After-Free.\n\nFix this by splitting the DMA release into two functions:\n\n1. __page_pool_unmap_netmem_dma() caches dma_addr before xa_cmpxchg(),\n   does the cmpxchg to remove the DMA mapping, and calls dma_unmap on\n   the cached address. It never touches netmem fields after the cmpxchg,\n   making it safe for the scrub path which holds no page ref.\n\n2. __page_pool_release_netmem_dma() wraps the above and additionally\n   clears dma_addr and DMA index bits in netmem fields. This is safe\n   only when the caller holds a page ref, so it is used by the return\n   path (page_pool_return_netmem).\n\nThe scrub path calls __page_pool_unmap_netmem_dma() directly; the return\npath calls __page_pool_release_netmem_dma().",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-90201"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/24ef02f934eeb48830cff6b739abc3c62b1d107b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/424a9fc4876cc7f28e9cb0aa8d92e920d726e350"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/9b65b0253ad5a66f73efee9a79a21a1e2b57cf59"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/bbfef303f980c1c078b8fa142e10a0e2fbcdd247"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-17T17:17:15Z"
  }
}