Description
In the Linux kernel, the following vulnerability has been resolved:
bpf: Fix memleak due to fentry attach failure
If it fails to attach fentry, the allocated bpf trampoline image will be left in the system. That can be verified by checking /proc/kallsyms.
This meamleak can be verified by a simple bpf program as follows:
SEC("fentry/trap_init") int fentry_run() { return 0; }
It will fail to attach trap_init because this function is freed after kernel init, and then we can find the trampoline image is left in the system by checking /proc/kallsyms.
$ tail /proc/kallsyms ffffffffc0613000 t bpf_trampoline_6442453466_1 [bpf] ffffffffc06c3000 t bpf_trampoline_6442453466_1 [bpf]
$ bpftool btf dump file /sys/kernel/btf/vmlinux | grep "FUNC 'trap_init'" [2522] FUNC 'trap_init' type_id=119 linkage=static
$ echo $((6442453466 & 0x7fffffff)) 2522
Note that there are two left bpf trampoline images, that is because the libbpf will fallback to raw tracepoint if -EINVAL is returned.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HWeakness enumeration
Affected software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= e21aa341785c679dd409c8cb71f864c00fe6c463, < 20109ddd5bea2c24d790debf5d02584ef24c3f5e; >= e21aa341785c679dd409c8cb71f864c00fe6c463, < f72c67d1a82dada7d6d504c806e111e913721a30; >= e21aa341785c679dd409c8cb71f864c00fe6c463, < 6aa27775db63ba8c7c73891c7dfb71ddc230c48d; >= e21aa341785c679dd409c8cb71f864c00fe6c463, < 108598c39eefbedc9882273ac0df96127a629220; e21d2b92354b3cd25dd774ebb0f0e52ff04a7861; 85d177f56e5256e14b74a65940f981f6e3e8bb32; >= 5.10.28, < 5.11; >= 5.11.11, < 5.12 |
| Linux | Linux | 5.12 |
References
- https://git.kernel.org/stable/c/108598c39eefbedc9882273ac0df96127a629220Patch
- https://git.kernel.org/stable/c/20109ddd5bea2c24d790debf5d02584ef24c3f5ePatch
- https://git.kernel.org/stable/c/6aa27775db63ba8c7c73891c7dfb71ddc230c48dPatch
- https://git.kernel.org/stable/c/f72c67d1a82dada7d6d504c806e111e913721a30Patch
Timeline
- Published
- Sep 15, 2025
- Last modified
- Jun 17, 2026
- NVD status
- Modified