# CVE-2026-99026: net: team: free skb when broadcast has no txable port


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** AZL-110882, BELL-CVE-2026-99026, DEBIAN-CVE-2026-99026, GHSA-c6m3-gh7v-93hm, UBUNTU-CVE-2026-99026

## What is CVE-2026-99026?

CVE-2026-99026 is a vulnerability in Linux, published on 23 Oct 2026. 

### Official 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.

## Which versions are affected by CVE-2026-99026?


## How do I fix CVE-2026-99026?

Upgrade to a fixed version.

## Is CVE-2026-99026 being exploited?

There is no known exploitation of CVE-2026-99026 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-99026 and fix it if it is affected.

What it is: CVE-2026-99026 is a vulnerability in Linux, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-99026 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-99026/ (Markdown: https://insights.sbomify.com/CVE-2026-99026/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-99026
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-99026
- OSV: https://osv.dev/vulnerability/CVE-2026-99026

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-99026/
Summaries are generated and may contain mistakes; the official description above is the record.