# CVE-2026-74413: wifi: rtw89: fix wrong pci_get_drvdata type in AER handlers

> Incorrect pointer type usage in rtw89 AER handlers causes memory corruption and potential system crashes during PCI error recovery.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/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-74413, DEBIAN-CVE-2026-74413, GHSA-cq4j-9r28-wxqg, UBUNTU-CVE-2026-74413

## What is CVE-2026-74413?

CVE-2026-74413 is a high-severity 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: rtw89: fix wrong pci_get_drvdata type in AER handlers

rtw89 stores an ieee80211_hw pointer via pci_set_drvdata() at probe
time, but io_error_detected() and io_resume() retrieve it as a
net_device pointer.  This causes netif_device_detach/attach to
operate on an ieee80211_hw struct, reading and writing at wrong
offsets.  The adjacent io_slot_reset() already does it correctly.

Use ieee80211_stop_queues/wake_queues instead, consistent with
every other queue stop/start path in the driver.

Tested on RTL8852CE by calling the handlers from a test module
before and after the fix.

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


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

Apply the vendor's patch.

## Is CVE-2026-74413 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74413 is a high-severity 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-74413 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-74413/ (Markdown: https://insights.sbomify.com/CVE-2026-74413/index.md)
```

## Sources

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

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