CVE-2023-53221
BaseFortify
Publication date: 2025-09-15
Last updated on: 2025-12-03
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 5.10.28 (inc) to 5.11 (exc) |
| linux | linux_kernel | From 5.11.11 (inc) to 5.12 (exc) |
| linux | linux_kernel | From 5.12.1 (inc) to 6.1.39 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.3.13 (exc) |
| linux | linux_kernel | From 6.4 (inc) to 6.4.4 (exc) |
| linux | linux_kernel | 5.12 |
| linux | linux_kernel | 5.12 |
| linux | linux_kernel | 5.12 |
| linux | linux_kernel | 5.12 |
| linux | linux_kernel | 5.12 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-401 | The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel involves a memory leak caused by a failure to attach a function entry (fentry) probe. When the kernel fails to attach the fentry probe, the allocated BPF trampoline image remains in the system instead of being freed. This leftover trampoline image can be observed in the system's /proc/kallsyms file. The issue occurs because the target function (trap_init) is freed after kernel initialization, causing the attach to fail and the memory allocated for the trampoline to leak.
How can this vulnerability impact me? :
The impact of this vulnerability is a memory leak in the Linux kernel due to leftover BPF trampoline images when fentry attach fails. Over time, this could lead to increased memory usage and potential resource exhaustion, which might degrade system performance or stability.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking for leftover BPF trampoline images in the system. You can verify this by examining the contents of /proc/kallsyms for entries like 'bpf_trampoline_*'. Example commands include: $ tail /proc/kallsyms $ bpftool btf dump file /sys/kernel/btf/vmlinux | grep "FUNC 'trap_init'" $ echo $((6442453466 & 0x7fffffff)) These commands help identify if the fentry attach to 'trap_init' failed and left trampoline images in the system.