# CVE-2026-81004: ipmi:msghandler: Cancel work cleanly on an error

> An attacker with local access could trigger a use-after-free in the Linux kernel IPMI driver during interface startup errors, potentially leading to code execution or system crash.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 11 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-81004, DEBIAN-CVE-2026-81004, GHSA-7w62-wjr5-jwfq, UBUNTU-CVE-2026-81004

## What is CVE-2026-81004?

CVE-2026-81004 is a high-severity use after free 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:

ipmi:msghandler: Cancel work cleanly on an error

If an error occurs during startup of an IPMI interface, it may have
scheduled work to run.  The work needs to be canceled before the
interface can be freed.

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


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

Apply the vendor's patch.

## Is CVE-2026-81004 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-81004 is a high-severity use after free 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-81004 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-81004/ (Markdown: https://insights.sbomify.com/CVE-2026-81004/index.md)
```

## Sources

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

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