# CVE-2026-98890: wifi: libertas: reject short monitor TX frames


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** AZL-110635, BELL-CVE-2026-98890, DEBIAN-CVE-2026-98890, GHSA-65v2-4hr3-h5j6, UBUNTU-CVE-2026-98890

## What is CVE-2026-98890?

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

### Official description

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

wifi: libertas: reject short monitor TX frames

In monitor mode, lbs_hard_start_xmit() casts skb->data to a
radiotap TX header, skips that header, and then copies the 802.11
destination address from offset 4 in the remaining frame.  The
generic length check only rejects zero-length and oversized skbs, so
a short monitor frame can be read past the end of the skb data.

Require enough bytes for the radiotap TX header and the destination
address field before using the monitor-mode header layout.

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


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

Upgrade to a fixed version.

## Is CVE-2026-98890 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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