# CVE-2026-98948: mlxsw: spectrum_flower: Fix port range register leak in tmplt_create()


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** AZL-110753, BELL-CVE-2026-98948, DEBIAN-CVE-2026-98948, GHSA-q8hc-4jgv-gvh5, UBUNTU-CVE-2026-98948

## What is CVE-2026-98948?

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

### Official description

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

mlxsw: spectrum_flower: Fix port range register leak in tmplt_create()

mlxsw_sp_flower_tmplt_create() parses a flow_cls_offload template
into a stack-local struct mlxsw_sp_acl_rule_info purely to compute
rulei.values.elusage. Parsing can acquire port range registers via
mlxsw_sp_flower_parse_ports_range(), but since this rulei never goes
through mlxsw_sp_acl_rulei_destroy(), those registers were never
released, including through chain template deletion.

Factor out of mlxsw_sp_acl_rulei_destroy() the code to actually
release the necessary resources and call from
mlxsw_sp_flower_tmplt_create() to plug the leak.

The issue was found during a review of Wentao Liang's patch referenced
below.

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


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

Upgrade to a fixed version.

## Is CVE-2026-98948 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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