GHSA-J482-JX6V-W2PF
Vulnerability from github – Published: 2026-10-18 18:31 – Updated: 2026-10-18 18:31In the Linux kernel, the following vulnerability has been resolved:
net: stmmac: clear stale buf->page after recycling on skb build failure
In stmmac_rx(), when napi_build_skb() fails the descriptor page is recycled back to the page pool with page_pool_recycle_direct(), but buf->page is left pointing at the recycled page, unlike every other consumption site in the function which clears the pointer after handing the page away.
With the stale pointer stmmac_rx_refill() skips the replacement allocation and programs the already-recycled page back into the RX descriptor.
Clear buf->page on the napi_build_skb() failure path to keep the buffer lifecycle consistent with the other consumption sites.
{
"affected": [],
"aliases": [
"CVE-2026-98571"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-18T16:17:09Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: stmmac: clear stale buf-\u003epage after recycling on skb build failure\n\nIn stmmac_rx(), when napi_build_skb() fails the descriptor page is\nrecycled back to the page pool with page_pool_recycle_direct(), but\nbuf-\u003epage is left pointing at the recycled page, unlike every other\nconsumption site in the function which clears the pointer after handing\nthe page away.\n\nWith the stale pointer stmmac_rx_refill() skips the replacement\nallocation and programs the already-recycled page back into the RX\ndescriptor.\n\nClear buf-\u003epage on the napi_build_skb() failure path to keep the buffer\nlifecycle consistent with the other consumption sites.",
"id": "GHSA-j482-jx6v-w2pf",
"modified": "2026-10-18T18:31:54Z",
"published": "2026-10-18T18:31:54Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98571"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/0a7822e34a0bfde31b194ac3da3253e5032b44cc"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/298673397ea3f6f5811b84f0d9f71eac71dda2e3"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/501baaeca7d128fa0a2f6953cf5873c5b0d7cf89"
}
],
"schema_version": "1.4.0",
"severity": []
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
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.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
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.
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.