wifi: mt76: mt7915: unlink TWT flow if the MCU rejects the agreement
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 3782b69d03e714b8ff98b84c7426d8cef0e64d7c · < 16a04441eab0dcd4d7126a6f66b370adbf28f96d| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
wifi: mt76: mt7915: unlink TWT flow if the MCU rejects the agreement
The flow is added to dev->twt_list before sending the agreement to the firmware, but the error path leaves it linked while flowid_mask is never set. The flow slot can then be reused and memset while still on the list, corrupting twt_list, and station removal leaves a dangling entry behind that mt7915_mac_twt_sched_list_add() later walks.
From the CVE record · Linux
The Linux kernel mt7915 Wi-Fi driver can leave a TWT flow linked after firmware rejects an agreement. Reusing the flow slot can corrupt the TWT list, and station removal can leave a dangling entry that is later traversed. The input does not specify how an attacker could trigger this or whether access or user interaction is required.
Engineers running Linux kernels with the mt7915 Wi-Fi driver should check their versions; affected versions are not specified.