CVE-2026-98105: Linux kernel · net: ethernet: oa_tc6: Improve the error recovery
Source GCVE Database
Not known to be exploited · CVSS 5.5 Medium · fixed in d33003e752f25c385f2cf21964123582a44f6818 : update Linux kernel when convenient.
Data as of 17 Nov 2026, 22:49 UTC
- Patch
- Available – fixed in d33003e752f25c385f2cf21964123582a44f6818, b89770d493749d7c3b8649996e1089719b4eff8d, 172c974113bffe5723b80b1acac17593bb50513c +1
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade Linux kernel to d33003e752f25c385f2cf21964123582a44f6818, b89770d493749d7c3b8649996e1089719b4eff8d, 172c974113bffe5723b80b1acac17593bb50513c or 9d3f6e714d5f8b728837f31bbe865b64cfd3216a.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In 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.
References
- nvd.nist.gov/vuln/detail/CVE-2026-98105 (opens in a new tab)
- git.kernel.org/stable/c/172c974113bffe5723b80b1acac17593bb50513c (opens in a new tab)
- git.kernel.org/stable/c/9d3f6e714d5f8b728837f31bbe865b64cfd3216a (opens in a new tab)
- git.kernel.org/stable/c/b89770d493749d7c3b8649996e1089719b4eff8d (opens in a new tab)
- git.kernel.org/stable/c/d33003e752f25c385f2cf21964123582a44f6818 (opens in a new tab)