CVE-2026-99045 json
ibmveth: h_free logical LAN on open-fail after register
published 19d ago modified 12d ago also EUVD-2026-108840
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 8%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 7.3
- linux Debian 13 6.12.113-1
- linux Debian 14 7.2.11-1
debian advisories DEBIAN-CVE-2026-99045
- linux Ubuntu 26.10 7.3.0-10.10
- linux-aws Ubuntu 26.10 7.3.0-1004.4
- linux-gcp Ubuntu 26.10 7.3.0-1004.4
- linux-raspi Ubuntu 26.10 7.3.0-1004.4
- linux-riscv Ubuntu 26.10 7.3.0-10.10.1
- linux-oracle Ubuntu 26.10 7.3.0-1004.4
- linux-realtime Ubuntu 26.10 7.3.0-10.10.1
ubuntu advisories UBUNTU-CVE-2026-99045
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/073df7871a7023298ce27cfa518fbc30cc155651 commit
- git.kernel.org/stable/c/7bd67d324d952101b3431c796d79f5e329bba159 commit
- git.kernel.org/stable/c/eae138e880686ce19879aa0d158fa3c73516f632 commit
- git.kernel.org/stable/c/decb4d4ead2c71ef698727734ab5024a872eb372 commit
- git.kernel.org/stable/c/c54bbdf6f0731102a4bf7f5e4ee535b3ea415996 commit
- git.kernel.org/stable/c/a065bd31ec462f6f9c267026b708dd020f122723 commit
- git.kernel.org/stable/c/d24fdec1413c656d29298097926e77542785ca0c commit
- git.kernel.org/stable/c/af0524bf4ce1a4cbd2946aa81751582951cfcab5 commit
Is CVE-2026-99045 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-99045 updated cvss 4.1
kernel: ibmveth: h_free logical LAN on open-fail after register
-
Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9affected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-11).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/073df7871a7023298ce27cfa518fbc30cc155651
- git.kernel.org /stable/c/7bd67d324d952101b3431c796d79f5e329bba159
- git.kernel.org /stable/c/eae138e880686ce19879aa0d158fa3c73516f632
- git.kernel.org /stable/c/decb4d4ead2c71ef698727734ab5024a872eb372
- git.kernel.org /stable/c/c54bbdf6f0731102a4bf7f5e4ee535b3ea415996
- git.kernel.org /stable/c/a065bd31ec462f6f9c267026b708dd020f122723
- git.kernel.org /stable/c/d24fdec1413c656d29298097926e77542785ca0c
- git.kernel.org /stable/c/af0524bf4ce1a4cbd2946aa81751582951cfcab5
Sources
- CVE List CVE-2026-99045
- NVD CVE-2026-99045
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.