CVE-2021-47274— tracing: Correct the length check which causes memory corruption
Affected Version Matrix 16
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| Linux | Linux | 2e584b1a02eeb860e286d39bc408b25ebc5ec844< edcce01e0e50840a9aa6a70baed21477bdd2c9f9 | affected |
e46d433754420b4d6513ca389403de88a0910279< 2d598902799886d67947406f26ee8e5fd2ca097f | affected | ||
0572fc6a510add9029b113239eaabf4b5bce8ec9< 31ceae385556c37e4d286cb6378696448f566883 | affected | ||
a0997a86f5c0085e183ddee5fb72091d584d3d16< d63f00ec908b3be635ead5d6029cc94246e1f38d | affected | ||
7c93d8cff582c459350d6f8906eea6e4cd60d959< 43c32c22254b9328d7abb1c2b0f689dc67838e60 | affected | ||
b220c049d5196dd94d992dd2dc8cba1a5e6123bf< b16a249eca2230c2cd66fa1d4b94743bd9b6ef92 | affected | ||
b220c049d5196dd94d992dd2dc8cba1a5e6123bf< 3e08a9f9760f4a70d633c328a76408e62d6f80a3 | affected | ||
5.11 | affected | ||
| … +8 more rows | |||
Get alerts for future matching vulnerabilitiesLog in to subscribe
I. Basic Information for CVE-2021-47274
Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗ Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
Vulnerability Title
tracing: Correct the length check which causes memory corruption
Source: NVD (National Vulnerability Database)
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: tracing: Correct the length check which causes memory corruption We've suffered from severe kernel crashes due to memory corruption on our production environment, like, Call Trace: [1640542.554277] general protection fault: 0000 [#1] SMP PTI [1640542.554856] CPU: 17 PID: 26996 Comm: python Kdump: loaded Tainted:G [1640542.556629] RIP: 0010:kmem_cache_alloc+0x90/0x190 [1640542.559074] RSP: 0018:ffffb16faa597df8 EFLAGS: 00010286 [1640542.559587] RAX: 0000000000000000 RBX: 0000000000400200 RCX: 0000000006e931bf [1640542.560323] RDX: 0000000006e931be RSI: 0000000000400200 RDI: ffff9a45ff004300 [1640542.560996] RBP: 0000000000400200 R08: 0000000000023420 R09: 0000000000000000 [1640542.561670] R10: 0000000000000000 R11: 0000000000000000 R12: ffffffff9a20608d [1640542.562366] R13: ffff9a45ff004300 R14: ffff9a45ff004300 R15: 696c662f65636976 [1640542.563128] FS: 00007f45d7c6f740(0000) GS:ffff9a45ff840000(0000) knlGS:0000000000000000 [1640542.563937] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [1640542.564557] CR2: 00007f45d71311a0 CR3: 000000189d63e004 CR4: 00000000003606e0 [1640542.565279] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [1640542.566069] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [1640542.566742] Call Trace: [1640542.567009] anon_vma_clone+0x5d/0x170 [1640542.567417] __split_vma+0x91/0x1a0 [1640542.567777] do_munmap+0x2c6/0x320 [1640542.568128] vm_munmap+0x54/0x70 [1640542.569990] __x64_sys_munmap+0x22/0x30 [1640542.572005] do_syscall_64+0x5b/0x1b0 [1640542.573724] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1640542.575642] RIP: 0033:0x7f45d6e61e27 James Wang has reproduced it stably on the latest 4.19 LTS. After some debugging, we finally proved that it's due to ftrace buffer out-of-bound access using a debug tool as follows: [ 86.775200] BUG: Out-of-bounds write at addr 0xffff88aefe8b7000 [ 86.780806] no_context+0xdf/0x3c0 [ 86.784327] __do_page_fault+0x252/0x470 [ 86.788367] do_page_fault+0x32/0x140 [ 86.792145] page_fault+0x1e/0x30 [ 86.795576] strncpy_from_unsafe+0x66/0xb0 [ 86.799789] fetch_memory_string+0x25/0x40 [ 86.804002] fetch_deref_string+0x51/0x60 [ 86.808134] kprobe_trace_func+0x32d/0x3a0 [ 86.812347] kprobe_dispatcher+0x45/0x50 [ 86.816385] kprobe_ftrace_handler+0x90/0xf0 [ 86.820779] ftrace_ops_assist_func+0xa1/0x140 [ 86.825340] 0xffffffffc00750bf [ 86.828603] do_sys_open+0x5/0x1f0 [ 86.832124] do_syscall_64+0x5b/0x1b0 [ 86.835900] entry_SYSCALL_64_after_hwframe+0x44/0xa9 commit b220c049d519 ("tracing: Check length before giving out the filter buffer") adds length check to protect trace data overflow introduced in 0fc1b09ff1ff, seems that this fix can't prevent overflow entirely, the length check should also take the sizeof entry->array[0] into account, since this array[0] is filled the length of trace data and occupy addtional space and risk overflow.
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞。攻击者利用该漏洞导致内存损坏。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)
Affected Products
II. Public POCs for CVE-2021-47274
| # | POC Description | Source Link | Shenlong Link |
|---|
AI-Generated POCPremium
No public POC found.
Login to generate AI POCIII. Intelligence Information for CVE-2021-47274
请登录查看更多情报信息。
Same Patch Batch · Linux · 2024-05-21 · 361 CVEs total
| CVE-2021-47432 | lib/generic-radix-tree.c: Don't overflow in peek() | |
| CVE-2023-52760 | gfs2: Fix slab-use-after-free in gfs2_qd_dealloc | |
| CVE-2023-52757 | smb: client: fix potential deadlock when releasing mids | |
| CVE-2023-52755 | ksmbd: fix slab out of bounds write in smb_inherit_dacl() | |
| CVE-2023-52754 | media: imon: fix access to invalid resource for the second interface | |
| CVE-2023-52753 | drm/amd/display: Avoid NULL dereference of timing generator | |
| CVE-2023-52752 | smb: client: fix use-after-free bug in cifs_debug_data_proc_show() | |
| CVE-2023-52751 | smb: client: fix use-after-free in smb2_query_info_compound() | |
| CVE-2023-52750 | arm64: Restrict CPU_BIG_ENDIAN to GNU as or LLVM IAS 15.x or newer | |
| CVE-2023-52749 | spi: Fix null dereference on suspend | |
| CVE-2023-52748 | f2fs: avoid format-overflow warning | |
| CVE-2022-48710 | drm/radeon: fix a possible null pointer dereference | |
| CVE-2023-52742 | net: USB: Fix wrong-direction WARNING in plusb.c | |
| CVE-2023-52738 | drm/amdgpu/fence: Fix oops due to non-matching drm_sched init/fini | |
| CVE-2023-52740 | powerpc/64s/interrupt: Fix interrupt exit race with security mitigation switch | |
| CVE-2023-52739 | Fix page corruption caused by racy check in __free_pages | |
| CVE-2023-52741 | cifs: Fix use-after-free in rdata->read_into_pages() | |
| CVE-2023-52743 | ice: Do not use WQ_MEM_RECLAIM flag for workqueue | |
| CVE-2023-52746 | xfrm/compat: prevent potential spectre v1 gadget in xfrm_xlate32_attr() | |
| CVE-2023-52747 | IB/hfi1: Restore allocated resources on failed copyout |
Showing top 20 of 361 CVEs. View all on vendor page → →
IV. Related Vulnerabilities
Same product: Linux
- CVE-2026-46333
ptrace: slightly saner 'get_dumpable()' logic - CVE-2026-43490
ksmbd: validate inherited ACE SID length - CVE-2026-43489
liveupdate: luo_file: remember retrieve() status - CVE-2026-43487
ata: libata-core: Disable LPM on ST1000DM010-2EP102 - CVE-2026-43488
usb: xhci: Prevent interrupt storm on host controller error
Same vendor: Linux
- CVE-2026-46333
ptrace: slightly saner 'get_dumpable()' logic - CVE-2026-43490
ksmbd: validate inherited ACE SID length - CVE-2026-43489
liveupdate: luo_file: remember retrieve() status - CVE-2026-43487
ata: libata-core: Disable LPM on ST1000DM010-2EP102 - CVE-2026-43488
usb: xhci: Prevent interrupt storm on host controller error
V. Comments for CVE-2021-47274
No comments yet