# CVE-2026-99029: net: sparx5: free the matchall entry on destroy


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** BELL-CVE-2026-99029, DEBIAN-CVE-2026-99029, GHSA-v4vf-8pf4-46v5, UBUNTU-CVE-2026-99029

## What is CVE-2026-99029?

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

### Official description

In the Linux kernel, the following vulnerability has been resolved:

net: sparx5: free the matchall entry on destroy

sparx5_tc_matchall_replace() allocates a struct sparx5_mall_entry for
every offloaded matchall filter and adds it to sparx5->mall_entries.
sparx5_tc_matchall_destroy() removes the entry from the list, but never
frees it, so the entry of every deleted mirror and goto matchall filter
is leaked.

Free the entry after unlinking it.

The leak was discovered by an AI code review agent, and reproduced with
kmemleak on a lan969x EV board (EV23X71A) by repeatedly adding and
deleting matchall mirror and goto filters. With the fix, kmemleak no
longer reports the leak.

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


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

Upgrade to a fixed version.

## Is CVE-2026-99029 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-99029 is a vulnerability in Linux, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-99029 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-99029/ (Markdown: https://insights.sbomify.com/CVE-2026-99029/index.md)
```

## Sources

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

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