GHSA-F226-MGWM-5X89
Vulnerability from github – Published: 2026-09-25 12:31 – Updated: 2026-09-25 12:31In the Linux kernel, the following vulnerability has been resolved:
net: ethernet: oa_tc6: Improve the error recovery
When oversubscribed traffic causes lot of buffer overflow errors, probably due to loss of data chunks, driver fails to find a data chunk with end_valid bit set, before it runs out of sk buffer space. As a result, assert is seen during skb_put.
Now, check is made if skb buffer has enough tailroom for the incoming data before accepting. If there is no room, current frame is abandoned and it will start looking for a data chunk with start_valid bit, that is a new frame.
SK buffer allocation error is considered as recoverable error.
rx_buf_overflow flag is too specific and no longer the only condition this flag is used for. Therefore it is renamed as wait_until_start_valid. This is more appropriate as this flag is used to look for the next data chunk with SV bit set, after failures like buffer overflow, buffer allocation failure, skb pointer validity besides buffer overflow error.
Not writing to status0 if it reads 0.
{
"affected": [],
"aliases": [
"CVE-2026-98105"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-25T11:17:40Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: ethernet: oa_tc6: Improve the error recovery\n\nWhen oversubscribed traffic causes lot of buffer overflow errors,\nprobably due to loss of data chunks, driver fails to find a\ndata chunk with end_valid bit set, before it runs out of sk buffer\nspace. As a result, assert is seen during skb_put.\n\nNow, check is made if skb buffer has enough tailroom for the\nincoming data before accepting. If there is no room, current\nframe is abandoned and it will start looking for a data chunk\nwith start_valid bit, that is a new frame.\n\nSK buffer allocation error is considered as recoverable error.\n\nrx_buf_overflow flag is too specific and no longer the only\ncondition this flag is used for. Therefore it is renamed as\nwait_until_start_valid. This is more appropriate as this flag\nis used to look for the next data chunk with SV bit set, after\nfailures like buffer overflow, buffer allocation failure, skb pointer\nvalidity besides buffer overflow error.\n\nNot writing to status0 if it reads 0.",
"id": "GHSA-f226-mgwm-5x89",
"modified": "2026-09-25T12:31:36Z",
"published": "2026-09-25T12:31:36Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98105"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/172c974113bffe5723b80b1acac17593bb50513c"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/9d3f6e714d5f8b728837f31bbe865b64cfd3216a"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/b89770d493749d7c3b8649996e1089719b4eff8d"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/d33003e752f25c385f2cf21964123582a44f6818"
}
],
"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.