VulnerabilityPublished 23 Oct 2026

CVE-2026-99026: Linux kernel · net: team: free skb when broadcast has no txable port

Source GCVE Database

Authoritative record:CVE-2026-99026· Medium

Not known to be exploited · fixed in f34b1bcac4581a5bd3daf9eff90f175e736b54aa : update Linux kernel when convenient.

Data as of 26 Oct 2026, 14:05 UTC

Severity

Medium

Rated by Threat Radar · 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-c6m3-gh7v-93hm

What to do

Upgrade Linux kernel to f34b1bcac4581a5bd3daf9eff90f175e736b54aa, 961563117626f4681623077ec0cfd86f86da0d49 or 489114c9ecae44e523361a4b3e610ee5ebd9189c.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 5fc889911a99043a97da1daa0d010ad72cbc3042, < f34b1bcac4581a5bd3daf9eff90f175e736b54aa	Fixed in f34b1bcac4581a5bd3daf9eff90f175e736b54aa
LinuxLinux	Affected ≥ 5fc889911a99043a97da1daa0d010ad72cbc3042, < 961563117626f4681623077ec0cfd86f86da0d49	Fixed in 961563117626f4681623077ec0cfd86f86da0d49
LinuxLinux	Affected ≥ 5fc889911a99043a97da1daa0d010ad72cbc3042, < 489114c9ecae44e523361a4b3e610ee5ebd9189c	Fixed in 489114c9ecae44e523361a4b3e610ee5ebd9189c
LinuxLinux	Affected =3.6	Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: net: team: free skb when broadcast has no txable port bc_transmit() sends the original skb through the last txable port. When no port is txable, it returns false without consuming the skb, but team_xmit() still returns NETDEV_TX_OK. AF_PACKET sends then retain the skb and its socket write-memory charge. A TX-enabled, link-down port keeps the broadcast transmit op installed. Carrier can stay up through a second link-up, TX-disabled port or be forced on by userspace. Free the original skb on the no-port path while leaving the existing drop accounting intact. Discovered by Sashiko during review of previous commit.

References

Community reviews

Loading reviews…