CVE-2026-43267
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
Linux kernel Affected 1 release
| Version | Status | Fixed in |
|---|---|---|
| — | Affected | 6.18.16 |
SUSE Affected 1 release
| Version | Status | Fixed in |
|---|---|---|
| — | Affected | — |
Windows Affected 1 release
| Version | Status | Fixed in |
|---|---|---|
| — | Affected | — |
Debian Fixed 5 releases
| Version | Status | Fixed in |
|---|---|---|
| trixie | Fixed | 0 |
| sid | Fixed | 6.19.6-1 |
| forky | Fixed | 6.19.6-1 |
| bullseye | Fixed | 0 |
| bookworm | Fixed | 0 |
References
- https://git.kernel.org/stable/c/1260bee01493126cf9c872b6ca2af261173baa6d
- https://git.kernel.org/stable/c/e00c9a4ec84c0bb067833b34202f457badbbc1c1
- https://git.kernel.org/stable/c/eb57be32f438c57c88d6ce756101c1dfbcc03bba
- https://www.suse.com/security/cve/CVE-2026-43267.html
- https://security-tracker.debian.org/tracker/CVE-2026-43267
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-43267
CWEs
CWE-369
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.