CVE-2026-93129: Linux kernel · platform/x86: dell-wmi-base: Fix handling of ultra performance key
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in adfd6846bea13667ff28f8aaf00c32fbd69825ab : update Linux kernel when convenient.
Data as of 26 Oct 2026, 15:59 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in adfd6846bea13667ff28f8aaf00c32fbd69825ab, ace1a687ea9ea70d17e3089ca173acfa1ec24412, 30674a7bbf20311a0c4edd5edb9526ef1eecc692 +2
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 to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: platform/x86: dell-wmi-base: Fix handling of ultra performance key The commit message of commit 5fbd827eb9c2 ("platform/x86: dell-wmi: Recognise or support new switches") states that the ultra performance key contains additional data after the type and code fields. The event data passed to dell_wmi_process_key() is already parsed, so "buffer" already starts after those two fields. Use the correct index for accessing the first data field to avoid a potential buffer overread.
References
- git.kernel.org/stable/c/30674a7bbf20311a0c4edd5edb9526ef1eecc692 (opens in a new tab)
- git.kernel.org/stable/c/ace1a687ea9ea70d17e3089ca173acfa1ec24412 (opens in a new tab)
- git.kernel.org/stable/c/16a82add1918d3aae1e0b68c0a983b6fc64f5062 (opens in a new tab)
- git.kernel.org/stable/c/392c19faec6bf4cb72fb02322e2a61e198dd8f72 (opens in a new tab)
- git.kernel.org/stable/c/adfd6846bea13667ff28f8aaf00c32fbd69825ab (opens in a new tab)