# CVE-2026-89444: platform/x86: dell-wmi-sysman: Don't hex dump attribute security buffer

> Local attackers with kernel log access can read plaintext admin passwords exposed by the Dell WMI sysman driver.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-100467, BELL-CVE-2026-89444, DEBIAN-CVE-2026-89444, GHSA-r3m2-c533-3mcx, UBUNTU-CVE-2026-89444

## What is CVE-2026-89444?

CVE-2026-89444 is a vulnerability in Linux, published on 11 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-sysman: Don't hex dump attribute security buffer

set_attribute() populates the security area of the BIOS attribute request
buffer with the current admin password via populate_security_buffer(), then
dumps the whole request buffer with print_hex_dump_bytes(). This can expose
the plaintext admin password in the kernel log.

The same issue was fixed for the password attribute path by
commit d1a196e0a6dc ("platform/x86: dell-wmi-sysman: Don't hex dump
plaintext password data"). Remove the remaining dump from the BIOS
attribute path.

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


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

Apply the vendor's patch.

## Is CVE-2026-89444 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89444 is a vulnerability in Linux, published on 11 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-89444 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-89444/ (Markdown: https://insights.sbomify.com/CVE-2026-89444/index.md)
```

## Sources

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

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