Kernel crash via incomplete ftrace buffer length check
Published May 21, 2024 · Updated Aug 5, 2026
Out-of-bounds write in Linux kernel ftrace allows attackers to corrupt kernel memory and crash the system via oversized trace data. The filter-buffer length check omits sizeof entry->array[0], even though that element stores the trace-data length, so string fetches can write past the allocation. Reachability requires CONFIG_KPROBE_EVENTS and an enabled kprobe that fetches an oversized string; the demonstrated consequence is a general-protection fault and kernel crash.
Summary
What happened
Out-of-bounds write in Linux kernel ftrace allows attackers to corrupt kernel memory and crash the system via oversized trace data. The filter-buffer length check omits sizeof entry->array[0], even though that element stores the trace-data length, so string fetches can write past the allocation. Reachability requires CONFIG_KPROBE_EVENTS and an enabled kprobe that fetches an oversized string; the demonstrated consequence is a general-protection fault and kernel crash.
The record
- CVE
- CVE-2021-47274
- Published
- May 21, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- May 21, 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=0572fc6a510add9029b113239eaabf4b5bce8ec9 <31ceae385556c37e4d286cb6378696448f566883
- Affected versionversion=2e584b1a02eeb860e286d39bc408b25ebc5ec844 <edcce01e0e50840a9aa6a70baed21477bdd2c9f9
- Affected versionversion=4.14.222 <4.14.237
- Affected versionversion=4.19.177 <4.19.195
- Affected versionversion=4.9.258 <4.9.273
- Affected versionversion=5.10.17 <5.10.44
- Affected versionversion=5.11
- Affected versionversion=5.4.99 <5.4.126
- Affected versionversion=7c93d8cff582c459350d6f8906eea6e4cd60d959 <43c32c22254b9328d7abb1c2b0f689dc67838e60
- Affected versionversion=a0997a86f5c0085e183ddee5fb72091d584d3d16 <d63f00ec908b3be635ead5d6029cc94246e1f38d
- Affected versionversion=b220c049d5196dd94d992dd2dc8cba1a5e6123bf <3e08a9f9760f4a70d633c328a76408e62d6f80a3
- Affected versionversion=b220c049d5196dd94d992dd2dc8cba1a5e6123bf <b16a249eca2230c2cd66fa1d4b94743bd9b6ef92
- Affected versionversion=e46d433754420b4d6513ca389403de88a0910279 <2d598902799886d67947406f26ee8e5fd2ca097f
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