Kernel panic via unlocked FTE active check
Published Dec 2, 2024 · Updated Aug 5, 2026
A race condition in Linux kernel mlx5 flow steering allows local users to trigger a kernel panic during flow-rule deletion. The fs_core deletion path reads an FTE active flag without holding the FTE lock, so a concurrent same-match addition attaches to an entry being removed and clears its hardware deletion callback prematurely. Triggering the race requires concurrent addition and deletion of rules with the same match value on an mlx5-backed flow table; the resulting panic interrupts the host.
Summary
What happened
A race condition in Linux kernel mlx5 flow steering allows local users to trigger a kernel panic during flow-rule deletion. The fs_core deletion path reads an FTE active flag without holding the FTE lock, so a concurrent same-match addition attaches to an entry being removed and clears its hardware deletion callback prematurely. Triggering the race requires concurrent addition and deletion of rules with the same match value on an mlx5-backed flow table; the resulting panic interrupts the host.
The record
- CVE
- CVE-2024-53121
- Published
- Dec 2, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-362, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 2, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 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.1
- Affected versionversion=718ce4d601dbf73b5dbe024a88c9e34168fe87f2 <094d1a2121cee1e85ab07d74388f94809dcfb5b9
- Affected versionversion=718ce4d601dbf73b5dbe024a88c9e34168fe87f2 <0d568258f99f2076ab02e9234cbabbd43e12f30e
- Affected versionversion=718ce4d601dbf73b5dbe024a88c9e34168fe87f2 <5b47c2f47c2fe921681f4a4fe2790375e6c04cdd
- Affected versionversion=718ce4d601dbf73b5dbe024a88c9e34168fe87f2 <933ef0d17f012b653e9e6006e3f50c8d0238b5ed
- Affected versionversion=718ce4d601dbf73b5dbe024a88c9e34168fe87f2 <9ca314419930f9135727e39d77e66262d5f7bef6
- Affected versionversion=718ce4d601dbf73b5dbe024a88c9e34168fe87f2 <a508c74ceae2f5a4647f67c362126516d6404ed9
- Affected versionversion=718ce4d601dbf73b5dbe024a88c9e34168fe87f2 <bfba288f53192db08c68d4c568db9783fb9cb838
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