Kernel warning via premature devlink health report
Published May 20, 2024 · Updated May 11, 2026
Improper initialization in the Linux mlx5 driver allows local users to trigger a kernel warning when firmware reports an error during probing. During mlx5 device probing, the driver calls devlink_health_report before registering devlink, so devlink_recover_notify reaches its WARN_ON. The condition requires an mlx5 device to report a nonfatal firmware error during probe; operational interruption depends on the kernel's warning policy.
Summary
What happened
Improper initialization in the Linux mlx5 driver allows local users to trigger a kernel warning when firmware reports an error during probing. During mlx5 device probing, the driver calls devlink_health_report before registering devlink, so devlink_recover_notify reaches its WARN_ON. The condition requires an mlx5 device to report a nonfatal firmware error during probe; operational interruption depends on the kernel's warning policy.
The record
- CVE
- CVE-2024-35961
- Published
- May 20, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 20, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 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=5.16
- Affected versionversion=cf530217408e3686f7002429769ede59dd931151 <8c91c60858473731bcdaf04fda99fcbcf84420d4
- Affected versionversion=cf530217408e3686f7002429769ede59dd931151 <967caa3d37c078e5b95a32094657e6a4cad145f0
- Affected versionversion=cf530217408e3686f7002429769ede59dd931151 <c6e77aa9dd82bc18a89bf49418f8f7e961cfccc8
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
No sourced classifications are available.
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