CVE-2026-98217

Description

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.

Is your site exposed to CVE-2026-98217?

Run a free security scan — no signup, results in seconds.

EPSS — Exploit Prediction

0.0018

Probability of exploitation

0.07%

Percentile rank

EPSS estimates the probability that this vulnerability will be exploited in the wild within the next 30 days. A higher score means more likely to be exploited.

References

Other References

https://git.kernel.org/stable/c/0c3482e965b18bc242e54e899d1c4d391ca8e5e3 https://git.kernel.org/stable/c/1af874e9f4ce22ccf8b10ab5462f32c70d3be21a https://git.kernel.org/stable/c/734f066933484f6c7cedea0312763249beed5845 https://git.kernel.org/stable/c/791471421d848ce13e84f4b21c9e19973d471c4e https://git.kernel.org/stable/c/a07bee32127d7c4cd3b1bb9a088e21d0c93634c9 https://git.kernel.org/stable/c/ced1186fea7c77e16681c7ef4802897885989c3b https://git.kernel.org/stable/c/cf20d7476754c00eec04ae23d3e929de33ce0345 https://git.kernel.org/stable/c/ffb80872617b5f9b3dd1536ec2909029fa66f228

Frequently Asked Questions

What is CVE-2026-98217? +

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.

How do I check if I'm vulnerable to CVE-2026-98217? +

You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.