CVE-2026-98217
Last modified
CVE-2026-98217 is a vulnerability of currently unknown severity. 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.
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.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= c1e7e466120b80ce49e91af0c9da1ce6dee4844a, < 791471421d848ce13e84f4b21c9e19973d471c4e; >= c1e7e466120b80ce49e91af0c9da1ce6dee4844a, < 734f066933484f6c7cedea0312763249beed5845; >= c1e7e466120b80ce49e91af0c9da1ce6dee4844a, < a07bee32127d7c4cd3b1bb9a088e21d0c93634c9; >= c1e7e466120b80ce49e91af0c9da1ce6dee4844a, < cf20d7476754c00eec04ae23d3e929de33ce0345; >= c1e7e466120b80ce49e91af0c9da1ce6dee4844a, < 0c3482e965b18bc242e54e899d1c4d391ca8e5e3; >= c1e7e466120b80ce49e91af0c9da1ce6dee4844a, < ffb80872617b5f9b3dd1536ec2909029fa66f228; >= c1e7e466120b80ce49e91af0c9da1ce6dee4844a, < ced1186fea7c77e16681c7ef4802897885989c3b; >= c1e7e466120b80ce49e91af0c9da1ce6dee4844a, < 1af874e9f4ce22ccf8b10ab5462f32c70d3be21a |
| Linux | Linux | 3.7 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-98217?
How severe is CVE-2026-98217?
How do I fix CVE-2026-98217?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-98211In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98212In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98213In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98214In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98215In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98216In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-98218In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98219In the Linux kernel, the following vulnerability has been re…
- CVE-2026-9822The WP Hotel Booking WordPress plugin before 2.3.1 does not …6.5
- CVE-2026-98220In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98221In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98222In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-98217?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
