# CVE-2026-93129: platform/x86: dell-wmi-base: Fix handling of ultra performance key

> A buffer overread in the Linux kernel's Dell WMI driver allows local attackers to read sensitive memory or cause a system crash.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-102485, BELL-CVE-2026-93129, DEBIAN-CVE-2026-93129, GHSA-3wx5-9x5h-8qmh, UBUNTU-CVE-2026-93129

## What is CVE-2026-93129?

CVE-2026-93129 is a memory corruption vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-93129?


## How do I fix CVE-2026-93129?

Apply the vendor's patch.

## Is CVE-2026-93129 being exploited?

There is no known exploitation of CVE-2026-93129 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93129 and fix it if it is affected.

What it is: CVE-2026-93129 is a memory corruption vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93129 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93129/ (Markdown: https://insights.sbomify.com/CVE-2026-93129/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93129
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93129
- OSV: https://osv.dev/vulnerability/CVE-2026-93129

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93129/
Summaries are generated and may contain mistakes; the official description above is the record.