Kernel compromise via dangling TWT flow reuse
Published Sep 17, 2026 · Updated Sep 18, 2026
Memory corruption in the Linux kernel mt7915 Wi-Fi driver allows attackers on the adjacent WLAN to compromise the host. An MCU-rejected TWT agreement remains on dev->twt_list without its flow ID being marked, so reuse clears a linked slot and station removal leaves a dangling entry. An associated client on an AP with TWT responder enabled can trigger kernel reads and writes through the corrupted list, ending in host compromise, a hang, or a panic.
Summary
What happened
Memory corruption in the Linux kernel mt7915 Wi-Fi driver allows attackers on the adjacent WLAN to compromise the host. An MCU-rejected TWT agreement remains on dev->twt_list without its flow ID being marked, so reuse clears a linked slot and station removal leaves a dangling entry. An associated client on an AP with TWT responder enabled can trigger kernel reads and writes through the corrupted list, ending in host compromise, a hang, or a panic.
The record
- CVE
- CVE-2026-90357
- Published
- Sep 17, 2026
- Updated
- Sep 18, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3782b69d03e714b8ff98b84c7426d8cef0e64d7c <16a04441eab0dcd4d7126a6f66b370adbf28f96d
- Affected versionversion=3782b69d03e714b8ff98b84c7426d8cef0e64d7c <1bd5c4ed2b9045faf83315c54cd37a9b7c71b5c7
- Affected versionversion=3782b69d03e714b8ff98b84c7426d8cef0e64d7c <6bce0f1280c94af8314f895f404629da09f0788c
- Affected versionversion=3782b69d03e714b8ff98b84c7426d8cef0e64d7c <beaa42b875965dbc3e80e46970e0bfa60a94c2db
- Affected versionversion=3782b69d03e714b8ff98b84c7426d8cef0e64d7c <c09d1b15ed2dc49060303b16a296b7b8b7794cbe
- Affected versionversion=3782b69d03e714b8ff98b84c7426d8cef0e64d7c <cabe239e95b4eebf5b6c3654087b66ff9425bc7b
- Affected versionversion=5.16
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started