CPU hang via zero-length firmware response TLV
Published Sep 17, 2026 · Updated Sep 17, 2026
DoS in the Linux kernel mt7996 driver allows attackers to hang a CPU via malformed firmware replies during device probe. The mt7996_mcu_get_chip_config function advances its response loop by an unchecked TLV length, allowing zero-length entries to prevent progress, and reads a u32 payload without bounds checking. Triggering requires an mt7996 device and a malformed firmware response; upstream describes a theoretical condition without establishing attacker control of that response.
Summary
What happened
DoS in the Linux kernel mt7996 driver allows attackers to hang a CPU via malformed firmware replies during device probe. The mt7996_mcu_get_chip_config function advances its response loop by an unchecked TLV length, allowing zero-length entries to prevent progress, and reads a u32 payload without bounds checking. Triggering requires an mt7996 device and a malformed firmware response; upstream describes a theoretical condition without establishing attacker control of that response.
The record
- CVE
- CVE-2026-90370
- Published
- Sep 17, 2026
- Updated
- Sep 17, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 17, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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