# wifi: rtw89: fix potential zero beacon interval in beacon tracking

CVE record · `CVE-2026-43267`

- **Identifiers:** `CVE-2026-43267`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 6 May 2026
- **Updated:** 6 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 6 May 2026, 11:28 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `d360551f265e3c942ce06cd6f4d2f7f67741bcbd to before 1260bee01493126cf9c872b6ca2af261173baa6d` (git)
  - affected: `d360551f265e3c942ce06cd6f4d2f7f67741bcbd to before e00c9a4ec84c0bb067833b34202f457badbbc1c1` (git)
  - affected: `d360551f265e3c942ce06cd6f4d2f7f67741bcbd to before eb57be32f438c57c88d6ce756101c1dfbcc03bba` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.18`
  - unaffected: `before 6.18` (semver)
  - unaffected: `6.18.16 to 6.18.*, inclusive` (semver)
  - unaffected: `6.19.6 to 6.19.*, inclusive` (semver)
  - unaffected: `7.0 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The rtw89 Wi-Fi driver in the Linux kernel is affected in version 6.18, and fixed versions are listed as 6.18.16, 6.19.6 and 7.0. A zero beacon interval can cause a division by zero during beacon tracking, but the source gives few details on what an attacker needs to trigger it. Upgrade to 6.18.16, 6.19.6, 7.0 or a later release.

Written 17 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0012, the 1st percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 6 May 2026, 11:28 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-43267)
- 6 May 2026, 12:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-43267)

## Sources

- [CVE List: CVE-2026-43267](https://www.cve.org/CVERecord?id=CVE-2026-43267)
- [NVD: CVE-2026-43267](https://nvd.nist.gov/vuln/detail/CVE-2026-43267)

### References from the CNA

- <https://git.kernel.org/stable/c/1260bee01493126cf9c872b6ca2af261173baa6d>
- <https://git.kernel.org/stable/c/e00c9a4ec84c0bb067833b34202f457badbbc1c1>
- <https://git.kernel.org/stable/c/eb57be32f438c57c88d6ce756101c1dfbcc03bba>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-43267>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-43267/>. Everything for agents: <https://agentprime.io/llms.txt>.
