GHSA-PVJ4-6QWF-8PWQ
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: macb: fix dma_alloc_coherent() leak on macb_alloc() error paths
Fix 3 leaks in macb_alloc() error paths: - Tx buffer allocated but crossing a 4G boundary: Tx leaked. - Rx buffer allocation fails: Tx leaked. - Rx buffer allocated but crossing a 4G boundary: Tx & Rx leaked.
This is because our error handling calls macb_free(bp) which in turn frees the buffers stored in bp->queues[0], but nothing has been stored in there. Fix by storing allocated buffers into bp->queues[0] ASAP.
{
"affected": [],
"aliases": [
"CVE-2026-98492"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-18T16:17:00Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: macb: fix dma_alloc_coherent() leak on macb_alloc() error paths\n\nFix 3 leaks in macb_alloc() error paths:\n- Tx buffer allocated but crossing a 4G boundary: Tx leaked.\n- Rx buffer allocation fails: Tx leaked.\n- Rx buffer allocated but crossing a 4G boundary: Tx \u0026 Rx leaked.\n\nThis is because our error handling calls macb_free(bp) which in turn\nfrees the buffers stored in bp-\u003equeues[0], but nothing has been stored\nin there. Fix by storing allocated buffers into bp-\u003equeues[0] ASAP.",
"id": "GHSA-pvj4-6qwf-8pwq",
"modified": "2026-10-18T18:31:51Z",
"published": "2026-10-18T18:31:51Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98492"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/23d42b9a3bcd55b17d3b371544fedc708c2397e9"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/259e6cbb6a097da8ced544ee92a6fbde35aa1338"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/bda487567d0b7b15dfa876511085c0666b9efad5"
}
],
"schema_version": "1.4.0",
"severity": []
}
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.
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.