Kernel panic via invalid receive-length warning
Published Sep 17, 2026 · Updated Sep 17, 2026
DoS in the Linux mt76x02 driver allows physically proximate attackers to crash the kernel via corrupted wireless frames. The receive-length bounds check rejects oversized frames but invokes WARN_ON_ONCE, tainting the kernel rather than silently discarding invalid input. Exposure requires compatible wireless hardware in monitor mode with fcsfail enabled; panic_on_warn turns the first warning into a kernel panic, while the bounds check still prevents an oversized-buffer access.
Summary
What happened
DoS in the Linux mt76x02 driver allows physically proximate attackers to crash the kernel via corrupted wireless frames. The receive-length bounds check rejects oversized frames but invokes WARN_ON_ONCE, tainting the kernel rather than silently discarding invalid input. Exposure requires compatible wireless hardware in monitor mode with fcsfail enabled; panic_on_warn turns the first warning into a kernel panic, while the bounds check still prevents an oversized-buffer access.
The record
- CVE
- CVE-2026-90382
- Published
- Sep 17, 2026
- Updated
- Sep 17, 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 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.16
- Affected versionversion=7bc04215a66b60e198aecaee8418f6d79fa19faa <17d6b89e09eac2d90272fceeba3644e92212e02f
- Affected versionversion=7bc04215a66b60e198aecaee8418f6d79fa19faa <2d31e332c13b1db7745a7bd9cf74bc105524bcac
- Affected versionversion=7bc04215a66b60e198aecaee8418f6d79fa19faa <61b1f6d92249bc34580ff19de7c69c805f82adca
- Affected versionversion=7bc04215a66b60e198aecaee8418f6d79fa19faa <6def491fe9c4e83aa8cba62d74e9d4ab751ee967
- Affected versionversion=7bc04215a66b60e198aecaee8418f6d79fa19faa <81497634d9f872fd3e8b03aada55574afff6f174
- Affected versionversion=7bc04215a66b60e198aecaee8418f6d79fa19faa <b6e7958602bd1acdb8ae92703b6689a28bcc9bc0
- Affected versionversion=7bc04215a66b60e198aecaee8418f6d79fa19faa <c65bbfc730df9ebf0fea8e286b0ad2dfab03dbfe
- Affected versionversion=7bc04215a66b60e198aecaee8418f6d79fa19faa <d55e7aede542c4c76ead82d37d0c112f21eb2ac2
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