CVE-2026-99026: Linux kernel · net: team: free skb when broadcast has no txable port
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f34b1bcac4581a5bd3daf9eff90f175e736b54aa : update Linux kernel when convenient.
Data as of 26 Oct 2026, 17:16 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in f34b1bcac4581a5bd3daf9eff90f175e736b54aa, 961563117626f4681623077ec0cfd86f86da0d49, 489114c9ecae44e523361a4b3e610ee5ebd9189c
Exploitation evidence
Disclosed: evidence found.
CVE published 23 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Upgrade Linux kernel to f34b1bcac4581a5bd3daf9eff90f175e736b54aa, 961563117626f4681623077ec0cfd86f86da0d49 or 489114c9ecae44e523361a4b3e610ee5ebd9189c.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available in the Linux kernel as indicated by the fixed commit versions. Users should update their Linux kernel to versions including these fixes to remediate the issue.
Description
A vulnerability in the Linux kernel's network team driver was fixed where broadcast packets could be leaked when no transmitable port was available. The function bc_transmit() failed to consume the socket buffer (skb) in this case, causing the socket write-memory charge to be retained improperly. This was addressed by freeing the skb on the no-port path while maintaining existing drop accounting.