Kernel crash via blktrace use-after-free race
Published May 21, 2024 · Updated May 11, 2026
Use-after-free in Linux blktrace allows local users to crash the kernel by racing trace removal with block I/O activity. The sysfs removal path frees a relay buffer while trace_note_tsk can still reach its blk_trace entry through running_trace_list and dereference the freed buffer. Reaching the race requires access to two block devices, BLKTRACE ioctls, sysfs trace controls, and precise concurrent timing.
Summary
What happened
Use-after-free in Linux blktrace allows local users to crash the kernel by racing trace removal with block I/O activity. The sysfs removal path frees a relay buffer while trace_note_tsk can still reach its blk_trace entry through running_trace_list and dereference the freed buffer. Reaching the race requires access to two block devices, BLKTRACE ioctls, sysfs trace controls, and precise concurrent timing.
The record
- CVE
- CVE-2021-47375
- Published
- May 21, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 21, 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=2.6.30
- Affected versionversion=c71a896154119f4ca9e89d6078f5f63ad60ef199 <3815fe7371d2411ce164281cef40d9fc7b323dee
- Affected versionversion=c71a896154119f4ca9e89d6078f5f63ad60ef199 <488da313edf3abea7f7733efe011c96b23740ab5
- Affected versionversion=c71a896154119f4ca9e89d6078f5f63ad60ef199 <5afedf670caf30a2b5a52da96eb7eac7dee6a9c9
- Affected versionversion=c71a896154119f4ca9e89d6078f5f63ad60ef199 <677e362ba807f3aafe6f405c07e0b37244da5222
- Affected versionversion=c71a896154119f4ca9e89d6078f5f63ad60ef199 <a5f8e86192612d0183047448d8bbe7918b3f1a26
- Affected versionversion=c71a896154119f4ca9e89d6078f5f63ad60ef199 <d56171d9360c0170c5c5f8f7e2362a2e999eca40
- Affected versionversion=c71a896154119f4ca9e89d6078f5f63ad60ef199 <dacfd5e4d1142bfb3809aab3634a375f6f373269
- Affected versionversion=c71a896154119f4ca9e89d6078f5f63ad60ef199 <ebb8d26d93c3ec3c7576c52a8373a2309423c069
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.
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