CVE-2026-98217: Linux kernel · IB/mlx4: Fix use-after-free on pkey sysfs registration failure
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in ffb80872617b5f9b3dd1536ec2909029fa66f228 : patch Linux kernel soon.
Data as of 26 Oct 2026, 14:05 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in ffb80872617b5f9b3dd1536ec2909029fa66f228, cf20d7476754c00eec04ae23d3e929de33ce0345, ced1186fea7c77e16681c7ef4802897885989c3b +5
Exploitation evidence
Disclosed: evidence found.
CVE published 6 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available and has been applied in multiple commits identified by their hashes. Users should update to a Linux kernel version that includes these fixes to remediate the vulnerability. No additional mitigation steps are indicated or required beyond applying the official patch.
Description
A use-after-free vulnerability in the Linux kernel's IB/mlx4 driver was fixed. The issue occurs when register_pkey_tree() ignores errors from register_one_pkey_tree(), leading to stale pointers being stored and later passed to kobject_put() during device cleanup. This flaw could cause a use-after-free condition. The fix clears parent pointers after a failed registration and skips unregistered trees during cleanup, preventing double cleanup of failed trees.
References
- git.kernel.org/stable/c/791471421d848ce13e84f4b21c9e19973d471c4e (opens in a new tab)
- git.kernel.org/stable/c/734f066933484f6c7cedea0312763249beed5845 (opens in a new tab)
- git.kernel.org/stable/c/a07bee32127d7c4cd3b1bb9a088e21d0c93634c9 (opens in a new tab)
- git.kernel.org/stable/c/cf20d7476754c00eec04ae23d3e929de33ce0345 (opens in a new tab)
- git.kernel.org/stable/c/0c3482e965b18bc242e54e899d1c4d391ca8e5e3 (opens in a new tab)
- git.kernel.org/stable/c/ffb80872617b5f9b3dd1536ec2909029fa66f228 (opens in a new tab)
- git.kernel.org/stable/c/ced1186fea7c77e16681c7ef4802897885989c3b (opens in a new tab)
- git.kernel.org/stable/c/1af874e9f4ce22ccf8b10ab5462f32c70d3be21a (opens in a new tab)