CVE-2026-98217
IB/mlx4: Fix use-after-free on pkey sysfs registration failure
No known exploitation. EPSS puts it in the 7th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ c1e7e466120b80ce49e91af0c9da1ce6dee4844a, < 791471421d848ce13e84f4b21c9e19973d471c4eUpgrade to: 791471421d848ce13e84f4b21c9e19973d471c4eAffected: ≥ c1e7e466120b80ce49e91af0c9da1ce6dee4844a, < 734f066933484f6c7cedea0312763249beed5845Upgrade to: 734f066933484f6c7cedea0312763249beed5845Affected: ≥ c1e7e466120b80ce49e91af0c9da1ce6dee4844a, < a07bee32127d7c4cd3b1bb9a088e21d0c93634c9Upgrade to: a07bee32127d7c4cd3b1bb9a088e21d0c93634c9Affected: ≥ c1e7e466120b80ce49e91af0c9da1ce6dee4844a, < cf20d7476754c00eec04ae23d3e929de33ce0345Upgrade to: cf20d7476754c00eec04ae23d3e929de33ce0345 + 4 more branchesStated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
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.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.2% chance of exploitation activity in the next 30 days, which ranks it in the 7th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
2 events over 0 days, from the signal feeds we watch.
- Publishedrecord updated
Affected products
Sources
References in the record
- git.kernel.org/stable/c/791471421d848ce13e84f4b21c9e19973d471c4e
- git.kernel.org/stable/c/734f066933484f6c7cedea0312763249beed5845
- git.kernel.org/stable/c/a07bee32127d7c4cd3b1bb9a088e21d0c93634c9
And 5 more references. See all after sign-in
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Linux, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI