CVE-2026-99026: net: team: free skb when broadcast has no txable port
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Fixed version: Linux Linux 489114c9ecae44e523361a4b3e610ee5ebd9189c, 961563117626f4681623077ec0cfd86f86da0d49, aec1d35d76ad883bae83c24707010115f38d02ac; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 489114c9ecae44e523361a4b3e610ee5ebd9189c, 961563117626f4681623077ec0cfd86f86da0d49, aec1d35d76ad883bae83c24707010115f38d02ac; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 23, 2026
- Updated
- Nov 10, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.6affected
- 5fc889911a99043a97da1daa0d010ad72cbc3042 and later · before aec1d35d76ad883bae83c24707010115f38d02acaffected · git
- 5fc889911a99043a97da1daa0d010ad72cbc3042 and later · before 961563117626f4681623077ec0cfd86f86da0d49affected · git
- 5fc889911a99043a97da1daa0d010ad72cbc3042 and later · before f34b1bcac4581a5bd3daf9eff90f175e736b54aaaffected · git
- 5fc889911a99043a97da1daa0d010ad72cbc3042 and later · before 489114c9ecae44e523361a4b3e610ee5ebd9189caffected · git
- before 3.6not affected · semver
- 6.12.117 and later · up to and including 6.12.*not affected · semver
- 6.18.57 and later · up to and including 6.18.*not affected · semver
- 7.2.11 and later · up to and including 7.2.*not affected · semver
- 7.3 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:14 | linux | before 7.2.11-1 | 7.2.11-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-99024Oct 23, 2026 · optee: register TEE devices only once fully initialized0Monitor
- ← EarlierCVE-2026-99025Oct 23, 2026 · openvswitch: fix soft lockup in the netlink flow dump0Monitor
- Later →CVE-2026-99027Oct 23, 2026 · net: team: stop reusing skb after queue override0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 489114c9ecae44e523361a4b3e610ee5ebd9189c | Vendor (CNA) |
| Linux Linux | 961563117626f4681623077ec0cfd86f86da0d49 | Vendor (CNA) |
| Linux Linux | aec1d35d76ad883bae83c24707010115f38d02ac | Vendor (CNA) |
| Linux Linux | f34b1bcac4581a5bd3daf9eff90f175e736b54aa | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| debian:linux | 7.2.11-1 · Debian:14 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 12, 2026+20 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1390 · Oct 26, 2026(Linux Kernel Güvenlik Bildirimi)
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (2)
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.