# CVE-2026-99045: ibmveth: h_free logical LAN on open-fail after register


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** AZL-110924, BELL-CVE-2026-99045, DEBIAN-CVE-2026-99045, GHSA-5hch-2jpc-2mcv, UBUNTU-CVE-2026-99045

## What is CVE-2026-99045?

CVE-2026-99045 is a vulnerability in Linux, published on 23 Oct 2026. 

### Official description

In the Linux kernel, the following vulnerability has been resolved:

ibmveth: h_free logical LAN on open-fail after register

ibmveth_open() registers the logical LAN, then allocates the RX
buffer pools. A pool failure jumps to out_free_buffer_pools without
h_free_logical_lan(), so PHYP still owns the buffer-list page when
it is unmapped. request_irq() failure already issued the hypercall
before taking the same label.

Move that h_free to the shared post-register unwind so both paths
deregister before the buffer list is unmapped.

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


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

Upgrade to a fixed version.

## Is CVE-2026-99045 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-99045 is a vulnerability in Linux, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-99045 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-99045/ (Markdown: https://insights.sbomify.com/CVE-2026-99045/index.md)
```

## Sources

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

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