CVE-2026-98217 json
IB/mlx4: Fix use-after-free on pkey sysfs registration failure
published last mo. modified 23d ago also EUVD-2026-93145
- 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 7%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
IB/mlx4: Fix use-after-free on pkey sysfs registration failure
register_pkey_tree() ignores errors from register_one_pkey_tree() and continues registering the remaining slaves. The per-slave error path has already released the pkey parent kobjects, but their pointers remain stored in the device. A later device cleanup therefore passes the stale pointers to kobject_put(), causing a use-after-free.
Clear the parent pointers after releasing a failed slave tree and skip unregistered trees during device cleanup. This preserves the existing best-effort registration behavior while preventing a second cleanup of the failed tree.
Patch / fix
- Linux Linux 7.3
- linux Debian 12 6.1.190-1
- linux Debian 13 6.12.113-1
- linux Debian 14 7.2.8-1
- linux-6.12 Debian 12 6.12.113-1~deb12u1
debian advisories DEBIAN-CVE-2026-98217
- linux Ubuntu 22.04 LTS 5.15.0-202.212
- linux Ubuntu 24.04 LTS 6.8.0-149.149
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 22.04 LTS 5.15.0-1119.126
- linux-aws Ubuntu 24.04 LTS 6.8.0-1069.74
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1120.130
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1073.81
ubuntu advisories UBUNTU-CVE-2026-98217
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
- kernel-source openSUSE Tumbleweed 7.2.10-1.1
opensuse advisories openSUSE-SU-2026:12131-1
- kernel Azure Linux 3.0 6.6.158.1-1
azure linux advisories AZL-106071
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/791471421d848ce13e84f4b21c9e19973d471c4e commit
- git.kernel.org/stable/c/734f066933484f6c7cedea0312763249beed5845 commit
- git.kernel.org/stable/c/a07bee32127d7c4cd3b1bb9a088e21d0c93634c9 commit
- git.kernel.org/stable/c/cf20d7476754c00eec04ae23d3e929de33ce0345 commit
- git.kernel.org/stable/c/0c3482e965b18bc242e54e899d1c4d391ca8e5e3 commit
- git.kernel.org/stable/c/ffb80872617b5f9b3dd1536ec2909029fa66f228 commit
- git.kernel.org/stable/c/ced1186fea7c77e16681c7ef4802897885989c3b commit
- git.kernel.org/stable/c/1af874e9f4ce22ccf8b10ab5462f32c70d3be21a commit
Is CVE-2026-98217 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-98217 updated cvss 4.7
kernel: IB/mlx4: Fix use-after-free on pkey sysfs registration failure
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: workaround, no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more 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 OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9affected: workaround, no fix available “Fix deferred”
-
Red Hat Enterprise Linux 10 kernelnot 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.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-11).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/791471421d848ce13e84f4b21c9e19973d471c4e
- git.kernel.org /stable/c/734f066933484f6c7cedea0312763249beed5845
- git.kernel.org /stable/c/a07bee32127d7c4cd3b1bb9a088e21d0c93634c9
- git.kernel.org /stable/c/cf20d7476754c00eec04ae23d3e929de33ce0345
- git.kernel.org /stable/c/0c3482e965b18bc242e54e899d1c4d391ca8e5e3
- git.kernel.org /stable/c/ffb80872617b5f9b3dd1536ec2909029fa66f228
- git.kernel.org /stable/c/ced1186fea7c77e16681c7ef4802897885989c3b
- git.kernel.org /stable/c/1af874e9f4ce22ccf8b10ab5462f32c70d3be21a
Sources
- CVE List CVE-2026-98217
- NVD CVE-2026-98217
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.