Driver initialization failure via unchecked CLC rule length
Published May 28, 2026 · Updated May 28, 2026
Integer underflow in the Linux Kernel mt7921 wireless driver allows local users to cause driver initialization failure. The __mt7921_mcu_set_clc loop subtracts a CLC rule length and header size from unsigned buf_len without first verifying that the combined offset fits. Reachability requires an affected kernel and MT7921 adapter; the reported result is an almost infinite loop or invalid power setting, with no reported code execution.
Summary
What happened
Integer underflow in the Linux Kernel mt7921 wireless driver allows local users to cause driver initialization failure. The __mt7921_mcu_set_clc loop subtracts a CLC rule length and header size from unsigned buf_len without first verifying that the combined offset fits. Reachability requires an affected kernel and MT7921 adapter; the reported result is an almost infinite loop or invalid power setting, with no reported code execution.
The record
- CVE
- CVE-2026-46136
- Published
- May 28, 2026
- Updated
- May 28, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-787, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 28, 2026CVE publishedPublication date reported by the CVE source.
- May 28, 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=0c9318d49e501a5d50b02bd91a4813bde2353488
- Affected versionversion=15173a1697236793e9e900b82fece6f99d41b2a7 <e451c325b000b9a0081fd93bc6d103d6943d4b55
- Affected versionversion=5c8cac512844ad593d31258e215908014381bee2
- Affected versionversion=6.1.75 <6.2
- Affected versionversion=6.6.14 <6.6.140
- Affected versionversion=6.7.2 <6.8
- Affected versionversion=6.8
- Affected versionversion=fa6ad88e023ddfa6c5dcdb466d159e89f451e305 <0aa63d33742b805d1a218d18d12b983cce4b2f7b
- Affected versionversion=fa6ad88e023ddfa6c5dcdb466d159e89f451e305 <5373f8b19e568b5c217832b9bbef165bd2b2df14
- Affected versionversion=fa6ad88e023ddfa6c5dcdb466d159e89f451e305 <90cc573fd2f46ddbc2c329e7814b5ba3deb7b939
- Affected versionversion=fa6ad88e023ddfa6c5dcdb466d159e89f451e305 <a0111847f0b4f6023f6dd320114697514e024ba3
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.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo