# CVE-2026-74410: wifi: rtw88: fix OOB read from firmware RX descriptor exceeding DMA buffer

> An out-of-bounds read in the rtw88 PCIe WiFi driver allows attackers to read memory or cause a crash via crafted firmware descriptors.

- **Severity:** High 8.1 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 16 Oct 2026
- **Also known as:** BELL-CVE-2026-74410, DEBIAN-CVE-2026-74410, GHSA-xfh3-hf97-85m6, UBUNTU-CVE-2026-74410

## What is CVE-2026-74410?

CVE-2026-74410 is a high-severity memory corruption vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

wifi: rtw88: fix OOB read from firmware RX descriptor exceeding DMA buffer

In rtw_pci_rx_napi(), new_len is computed as the sum of pkt_len (14-bit
descriptor field, max 16383) and pkt_offset (drv_info_sz + shift, both
firmware-controlled). The result can exceed RTK_PCI_RX_BUF_SIZE (11478),
causing an out-of-bounds read from the pre-allocated DMA buffer when
skb_put_data copies new_len bytes. The USB transport already validates
this (rtw_usb_rx_data_put checks against RTW_USB_MAX_RECVBUF_SZ); the
PCIe path does not.

Add a check that new_len does not exceed the DMA buffer size.

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


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

Apply the vendor's patch.

## Is CVE-2026-74410 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74410 is a high-severity memory corruption vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-74410 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-74410/ (Markdown: https://insights.sbomify.com/CVE-2026-74410/index.md)
```

## Sources

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

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