CVE-2026-90346: wifi: nl80211: clean up color-change beacon data on errors

Published Sep 17, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

wifi: nl80211: clean up color-change beacon data on errors

nl80211colorchange() calls nl80211parsebeacon() for the beaconnext template, which can allocate params.beaconnext.mbssidies and .rnries. A parsing failure returned directly instead of using the out: cleanup, leaking any allocations completed before the error.

Allocate the nested attribute table before parsing beaconnext. Its allocation failure can then return before beacon data exists, while a later parsing failure uses out: to release the parsed data.

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    In nl80211_color_change()/nl80211_parse_beacon() for the beacon_next template: allocate the nested attribute table before parsing beacon_next, and ensure that on later parsing failures the out: cleanup path releases any allocations made before the error (including params.beacon_next.mbssid_ies and .rnr_ies).

    Linux kernel (nl80211) cleanup of color-change beacon data on parsing/allocation errors = Implement proper cleanup path (allocate nested attribute table before parsing beacon_next; ensure parsed beacon_next data is cleaned on errors rather than leaking allocations).

Event History

Sep 17, 2026
CVE Published
via MITRE·04:08 PM
Data Sourced
via MITRE·04:08 PM
Description

Frequently Asked Questions

1

What conditions are required to trigger the leak?

The error path is reached when parsing the beacon_next template in nl80211_color_change() fails after nl80211_parse_beacon() has already allocated MBSSID or RNR information-element data.

2

What is the impact of the vulnerable behavior?

Allocated beacon_next.mbssid_ies and beacon_next.rnr_ies data can be leaked when parsing fails, because the function returned without reaching its cleanup path.

3

How does the fix prevent the leak?

The nested attribute table is allocated before beacon_next parsing, so failure of that allocation occurs before beacon data exists. Later parsing failures are routed through the out cleanup path, which releases parsed beacon data.

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