# CVE-2026-98911: dpaa2-switch: fix the error path in dpaa2_switch_rx()


- **Severity:** High 7.5 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** AZL-110677, BELL-CVE-2026-98911, DEBIAN-CVE-2026-98911, GHSA-2gxg-jvpv-v5rf, UBUNTU-CVE-2026-98911

## What is CVE-2026-98911?

CVE-2026-98911 is a high-severity vulnerability in Linux, published on 23 Oct 2026. 

### Official description

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

dpaa2-switch: fix the error path in dpaa2_switch_rx()

In case of an error in dpaa2_switch_rx(), the dpaa2_switch_free_fd()
function is called in order to free the FD. This is incorrect since the
dpaa2_switch_free_fd() is intended to be used on Tx frame descriptors,
meaning that it expects in the software annotation area of the FD data
to find a valid skb pointer on which to call dev_kfree_skb().

Fix this by extracting the dma_unmap_page() from
dpaa2_switch_build_linear_skb() directly into the dpaa2_switch_rx()
function. This allows us to directly use free_pages() in case of an
error before an SKB was created and kfree_skb() afterwards.

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


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

Upgrade to a fixed version.

## Is CVE-2026-98911 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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