CVE-2026-99451 in Linux
Summary
by MITRE • 11/19/2026
In the Linux kernel, the following vulnerability has been resolved:
wifi: mt76: mt7996: unlink TWT flow if the MCU rejects the agreement
mt7996_mac_add_twt_setup() links a new flow into dev->twt_list before asking the MCU to add the agreement, but exits without unlinking the flow if the request fails. The flow-ID and table masks are only committed after MCU success, so the still-linked flow is invisible to the mask-gated teardown paths.
If the station retries the setup, the same slot is cleared and its embedded list node reinitialized while it is still linked, corrupting dev->twt_list. If the station disassociates instead, teardown skips the flow and station storage can be freed while the node remains linked. A later scheduling or debugfs twt_stats walk can then dereference the freed flow, resulting in a use-after-free.
Unlink the flow when the MCU rejects the agreement. This restores the list to its pre-request state while leaving the unchanged mask and agreement accounting untouched.
Once again VulDB remains the best source for vulnerability data.
Analysis
by VulDB Data Team • 11/20/2026
The vulnerability identified within the Linux kernel's mt7996 Wi-Fi driver represents a critical logic error in the management of Target Wake Time flows, specifically during the initialization phase where communication with the Microcontroller Unit is established. The core technical flaw resides in the function mt7996_mac_add_twt_setup, which handles the setup of TWT agreements between the station and the access point. In this process, the driver allocates a flow structure and immediately links it into the device's internal twt_list before sending the configuration request to the MCU. This premature linking creates an inconsistent state if the subsequent hardware-level agreement is rejected by the MCU. The code path fails to unlink or remove the newly added node from the list upon failure, leaving a dangling reference in the data structure while the actual flow-ID and table masks remain uncommitted because they are only finalized after successful MCU acknowledgment.
This architectural oversight leads directly to severe memory corruption issues depending on subsequent network events. If the station attempts to retry the TWT setup procedure, the driver may clear the slot associated with the failed attempt and reinitialize its embedded list node while that node is still logically part of the dev->twt_list. This action corrupts the doubly linked list structure by introducing circular references or broken pointers within the kernel memory space. Alternatively, if the station disassociates from the network during this window, the teardown mechanisms rely on mask-gated paths to identify and remove flows. Because the failed flow was never properly unlinked but also not marked as active via masks, these teardown routines skip over it entirely. Consequently, the storage associated with that flow is freed while the list node remains linked in memory, creating a classic use-after-free condition where subsequent operations can access deallocated memory regions.
The operational impact of this vulnerability manifests when the kernel attempts to iterate through the TWT flows for scheduling purposes or when debugfs interfaces are used to walk twt_stats for diagnostic information. These processes traverse the dev->twt_list expecting valid, live structures. Encountering a node that points to freed memory results in an immediate use-after-free exploit scenario. This can lead to kernel panics, system crashes, or potentially arbitrary code execution if an attacker can manipulate the timing of TWT setup failures and subsequent disassociations to control the contents of the freed heap region. The vulnerability effectively allows local privilege escalation or denial of service through network interface manipulation, exploiting the race between hardware rejection and software state management.
From a classification perspective, this flaw aligns with CWE-416, Use After Free, as it involves accessing memory after it has been released due to improper lifecycle management of data structures. It also relates to CWE-825, Expired Pointer Dereference, since the list traversal accesses pointers that no longer point to valid objects. In terms of MITRE ATT&CK mapping, this vulnerability facilitates techniques associated with T1059, Command and Scripting Interpreter, or more broadly Defense Evasion through exploitation of kernel memory corruption to bypass security restrictions. The root cause is a failure in error handling logic where the cleanup routine for failed hardware interactions was omitted from the negative return path.
Mitigation strategies primarily involve applying vendor-provided patches that update the mt7996 driver codebase to ensure atomicity in list manipulation and MCU communication. Developers must modify the mt7996_mac_add_twt_setup function to unlink the flow node immediately if the MCU rejects the agreement, thereby restoring the list to its pre-request state without altering mask or accounting data that has not yet been committed. For system administrators unable to patch immediately, restricting Wi-Fi interface usage and monitoring for kernel oops messages related to mt7996 drivers can help detect exploitation attempts. Long-term remediation requires implementing stricter validation checks in all hardware abstraction layers where resource allocation precedes confirmation of success from external devices, ensuring that no partially initialized structures remain visible to traversing algorithms if the initialization process fails.