Service interruption via stale eswitch notifier registration
Published Nov 5, 2024 · Updated May 23, 2026
Improper notifier cleanup in Linux kernel mlx5 eswitch initialization allows local users to interrupt service during repeated SR-IOV setup. The mlx5_eswitch_enable_locked failure path leaves eswitch_vport_event registered in the atomic notifier chain instead of unregistering it before returning. Reaching the fault requires local permission to reconfigure mlx5 SR-IOV after an initialization failure; another enable attempt triggers duplicate-registration warnings and can disrupt kernel availability.
Summary
What happened
Improper notifier cleanup in Linux kernel mlx5 eswitch initialization allows local users to interrupt service during repeated SR-IOV setup. The mlx5_eswitch_enable_locked failure path leaves eswitch_vport_event registered in the atomic notifier chain instead of unregistering it before returning. Reaching the fault requires local permission to reconfigure mlx5 SR-IOV after an initialization failure; another enable attempt triggers duplicate-registration warnings and can disrupt kernel availability.
The record
- CVE
- CVE-2024-50136
- Published
- Nov 5, 2024
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 5, 2024CVE publishedPublication date reported by the CVE source.
- May 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0aa1e83a20f12e9eaad32f72212ebc7fe0c29c95 <e58fb7ddbab6635191c26dea1af26b91cce00866
- Affected versionversion=6.1.60 <6.1.115
- Affected versionversion=6.5.9 <6.6
- Affected versionversion=6.6
- Affected versionversion=7624e58a8b3a251e3e5108b32f2183b34453db32 <1da9cfd6c41c2e6bbe624d0568644e1521c33e12
- Affected versionversion=7624e58a8b3a251e3e5108b32f2183b34453db32 <599147722c5778c96292e2fbff4103abbdb45b1f
- Affected versionversion=7624e58a8b3a251e3e5108b32f2183b34453db32 <9f2ccb6f3888bec45c00121ee43e4e72423b12c1
- Affected versionversion=dc426bd9d813aa5754ce35adaa6f97f0585c06fc
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo