Service crash via MCTP device teardown race
Published Jun 28, 2023 · Updated Mar 10, 2025
Use-after-free in Linux kernel 5.15 through 5.18-rc4 allows local users to crash the kernel by racing MCTP device teardown with sends. mctp_unregister() frees mdev->addrs while mctp_sendmsg() can retain a route and read the freed address array in mctp_local_output(). CAP_NET_ADMIN is required to fake device detachment; a successful race causes a kernel use-after-free and service crash.
Summary
What happened
Use-after-free in Linux kernel 5.15 through 5.18-rc4 allows local users to crash the kernel by racing MCTP device teardown with sends. mctp_unregister() frees mdev->addrs while mctp_sendmsg() can retain a route and read the freed address array in mctp_local_output(). CAP_NET_ADMIN is required to fake device detachment; a successful race causes a kernel use-after-free and service crash.
The record
- CVE
- CVE-2023-3439
- Published
- Jun 28, 2023
- Updated
- Mar 10, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416, T1499
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jun 28, 2023CVE publishedPublication date reported by the CVE source.
- Mar 10, 2025Record 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=Fixed in kernel 5.18-rc5
What conditions does exploitation require?
What is affected?
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.
Public exploit references
- CVE-2023-3439 MCTP race proof of conceptproof of concept · demonstrated
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