# CVE-2026-98908: net: microchip: sparx5: clean up PSFP resources on flower setup failure


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** AZL-110668, BELL-CVE-2026-98908, DEBIAN-CVE-2026-98908, GHSA-5v3g-9pp6-f3cf, UBUNTU-CVE-2026-98908

## What is CVE-2026-98908?

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

### Official description

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

net: microchip: sparx5: clean up PSFP resources on flower setup failure

sparx5_tc_flower_psfp_setup() allocates PSFP stream gate, flow meter and
stream filter resources before adding VCAP actions. If a later step
fails, the resources allocated earlier in the function are not unwound.

Add error paths to release the stream filter, flow meter and stream gate
when setup fails after they have been acquired.

Also make sparx5_psfp_fm_add() return the acquired flow-meter id before
the existing-flow-meter early return. When an existing flow meter is
reused, sparx5_psfp_fm_get() increments its pool reference count, but the
caller previously kept psfp_fmid as 0. If a later setup step failed, the
error path could try to delete flow-meter id 0 instead of the reused flow
meter, leaving the incremented reference behind.

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


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

Upgrade to a fixed version.

## Is CVE-2026-98908 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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