CVE-2026-98217: IB/mlx4: Fix use-after-free on pkey sysfs registration failure

Published Oct 6, 2026

Updated

IB/mlx4: Fix use-after-free on pkey sysfs registration failure

Affected Software

1 affected component

Linux Linux kernel

Event History

Oct 6, 2026

CVE Published

via MITRE·08:44 AM

Data Sourced

via MITRE·08:44 AM

Description

Data Sourced

via NVD·09:18 AM

Description

Oct 7, 2026

Data Sourced

via Microsoft·08:16 AM

DescriptionSeverityWeakness

Frequently Asked Questions

What condition is required to trigger the use-after-free?

Registration of a per-slave pkey sysfs tree must fail. The driver then continues registering other slaves while retaining stale parent kobject pointers for the failed tree, and a later device cleanup can invoke kobject_put() on those stale pointers.

Does a failed pkey sysfs registration stop registration for other slaves?

No. The existing behavior is best-effort: registration continues for remaining slaves even when one slave tree registration fails. The fix clears the failed tree's parent pointers so cleanup skips trees that were not successfully registered.

How can an affected system be identified from the available information?

The described failure path involves the Linux kernel IB/mlx4 driver and pkey sysfs tree registration for slaves. The supplied data does not provide affected kernel version ranges or observable logs or indicators.

CVE-2026-98217: IB/mlx4: Fix use-after-free on pkey sysfs registration failure

Affected Software

Event History

Frequently Asked Questions

What condition is required to trigger the use-after-free?

Does a failed pkey sysfs registration stop registration for other slaves?

How can an affected system be identified from the available information?

Company

Resources

Contact

Frequently Asked Questions

What condition is required to trigger the use-after-free?

Does a failed pkey sysfs registration stop registration for other slaves?

How can an affected system be identified from the available information?