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

Published May 6, 2026
·
Updated

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 bssconf->beaconint 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.

Affected Software

4 affected componentsFixes available
Linux Linux kernel (rtw89 driver)
Linux Linux kernel>=6.18<6.18.16
Linux Linux kernel>=6.19<6.19.6
Microsoft azl3 kernel 6.6.137.1-2

Event History

May 6, 2026
CVE Published
via MITRE·11:28 AM
Data Sourced
via MITRE·11:28 AM
Description
Data Sourced
via NVD·12:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
May 7, 2026
Data Sourced
via Microsoft·08:09 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:09 AM
DescriptionSeverity
Mar 28, 58325
Event
via Microsoft·03:35 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-43267?

CVE-2026-43267 has not been assigned a specific severity rating yet, as it requires analysis of its potential impact in various scenarios.

2

How do I fix CVE-2026-43267?

To fix CVE-2026-43267, update the Linux kernel to a version that includes the patch addressing the beacon tracking issue.

3

What software is affected by CVE-2026-43267?

CVE-2026-43267 affects the Linux kernel, specifically the rtw89 driver, in certain versions between 6.18 and 6.19.

4

What is the nature of the vulnerability in CVE-2026-43267?

CVE-2026-43267 involves a potential zero beacon interval in beacon tracking that could lead to various Wi-Fi connectivity issues.

5

Was CVE-2026-43267 resolved in a recent update?

Yes, CVE-2026-43267 was resolved in a recent update of the Linux kernel that fixed the beacon tracking issue.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203