FKIE_CVE-2026-90201
Vulnerability from fkie_nvd - Published: 2026-09-17 17:17 - Updated: 2026-09-17 17:17
Severity
Summary
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
Impacted products
| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"net/core/page_pool.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "bbfef303f980c1c078b8fa142e10a0e2fbcdd247",
"status": "affected",
"version": "4f51fb0d257ff4d406ec27966902de075e3b118e",
"versionType": "git"
},
{
"lessThan": "424a9fc4876cc7f28e9cb0aa8d92e920d726e350",
"status": "affected",
"version": "ee62ce7a1d909ccba0399680a03c2dee83bcae95",
"versionType": "git"
},
{
"lessThan": "9b65b0253ad5a66f73efee9a79a21a1e2b57cf59",
"status": "affected",
"version": "ee62ce7a1d909ccba0399680a03c2dee83bcae95",
"versionType": "git"
},
{
"lessThan": "24ef02f934eeb48830cff6b739abc3c62b1d107b",
"status": "affected",
"version": "ee62ce7a1d909ccba0399680a03c2dee83bcae95",
"versionType": "git"
},
{
"status": "affected",
"version": "c30ae60f41f9edd6e1b5cad41cf28ce04dae39e4",
"versionType": "git"
},
{
"lessThan": "6.12.110",
"status": "affected",
"version": "6.12.34",
"versionType": "semver"
},
{
"lessThan": "6.16",
"status": "affected",
"version": "6.15.3",
"versionType": "semver"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"net/core/page_pool.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.16"
},
{
"lessThan": "6.16",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.110",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.52",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.2.*",
"status": "unaffected",
"version": "7.2.6",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.3-rc1",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "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-\u003edma_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()."
}
],
"id": "CVE-2026-90201",
"lastModified": "2026-09-17T17:17:15.053",
"metrics": {},
"published": "2026-09-17T17:17:15.053",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/24ef02f934eeb48830cff6b739abc3c62b1d107b"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/424a9fc4876cc7f28e9cb0aa8d92e920d726e350"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/9b65b0253ad5a66f73efee9a79a21a1e2b57cf59"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/bbfef303f980c1c078b8fa142e10a0e2fbcdd247"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.
Loading…