CVE-2026-93124: Linux kernel · platform/x86: asus-wireless: Fail probe when there is no ACPI match
Affects Linux kernelSource CVE Database V5
Not known to be exploited : upgrade to 7bfa711f311a584002e16ecd750627306deb805c or 4aefd66ef7822cf7d3f53146dcee0b71021ed2b7 when convenient.
Data as of 26 Oct 2026, 14:34 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 7bfa711f311a584002e16ecd750627306deb805c, 4aefd66ef7822cf7d3f53146dcee0b71021ed2b7
Exploitation evidence
Disclosed: evidence found.
CVE published 17 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Linux kernel to 7bfa711f311a584002e16ecd750627306deb805c or 4aefd66ef7822cf7d3f53146dcee0b71021ed2b7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available in the Linux kernel as indicated by the fixed commit versions (7bfa711f311a584002e16ecd750627306deb805c and 4aefd66ef7822cf7d3f53146dcee0b71021ed2b7). Users should update to a kernel version that includes these fixes. No other mitigation is required as the issue is resolved by the official patch.
Description
CVE-2026-93124 is a vulnerability in the Linux kernel's asus-wireless platform driver where the probe function incorrectly succeeds when there is no ACPI device match. This leads to an input device being registered without a notify handler, causing it to never report events. Additionally, if the driver is force-bound to a device lacking an ACPI companion, it stores a NULL pointer that later causes a NULL pointer dereference during unbind.