GHSA-V487-W46V-372V
Vulnerability from github – Published: 2026-08-15 15:30 – Updated: 2026-08-17 06:33
VLAI
Details
In the Linux kernel, the following vulnerability has been resolved:
rtase: fix double free of multi-frag skb on DMA map failure
In rtase_start_xmit(), when the head buffer DMA mapping fails after rtase_xmit_frags() has mapped all fragments, the error path clears the fragment descriptors with rtase_tx_clear_range(), which frees the skb through the last-frag slot and accounts tx_dropped. Control then falls through to the common error label, which frees the same skb a second time and counts it again.
Return right after clearing the fragments when the skb owns frags; the no-frag case still drops through and frees the head skb once.
Severity
9.8 (Critical)
{
"affected": [],
"aliases": [
"CVE-2026-74545"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-15T13:17:59Z",
"severity": "CRITICAL"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nrtase: fix double free of multi-frag skb on DMA map failure\n\nIn rtase_start_xmit(), when the head buffer DMA mapping fails after\nrtase_xmit_frags() has mapped all fragments, the error path clears\nthe fragment descriptors with rtase_tx_clear_range(), which frees\nthe skb through the last-frag slot and accounts tx_dropped. Control\nthen falls through to the common error label, which frees the same\nskb a second time and counts it again.\n\nReturn right after clearing the fragments when the skb owns frags;\nthe no-frag case still drops through and frees the head skb once.",
"id": "GHSA-v487-w46v-372v",
"modified": "2026-08-17T06:33:52Z",
"published": "2026-08-15T15:30:36Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-74545"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/4f09172aff5f73a5e914f4fbc0d00a1c2ea9f7cb"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/6fb7b769d6ed6d1d2e02af4a80e57a2477f35086"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/db986098f30881fafcc752800aa3b13fd289c922"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/de691dc3227b061c4d0beba9f0128fe1ff33dd68"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
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…
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.
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.
Loading…
Loading…