bpf: Fix memleak due to fentry attach failure
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel f72c67d1a82dada7d6d504c806e111e913721a30, Kernel 5.11, Kernel 5.12 and 6 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=e21aa341785c679dd409c8cb71f864c00fe6c463 <f72c67d1a82dada7d6d504c806e111e913721a30, >=5.10.28 <5.11, >=5.11.11 <5.12, >=e21aa341785c679dd409c8cb71f864c00fe6c463 <108598c39eefbedc9882273ac0df96127a629220, >=e21aa341785c679dd409c8cb71f864c00fe6c463 <20109ddd5bea2c24d790debf5d02584ef24c3f5e, >=e21aa341785c679dd409c8cb71f864c00fe6c463 <6aa27775db63ba8c7c73891c7dfb71ddc230c48d, =5.12, =85d177f56e5256e14b74a65940f981f6e3e8bb32, =e21d2b92354b3cd25dd774ebb0f0e52ff04a7861 | f72c67d1a82dada7d6d504c806e111e913721a30, 5.11, 5.12, 108598c39eefbedc9882273ac0df96127a629220, 20109ddd5bea2c24d790debf5d02584ef24c3f5e, 6aa27775db63ba8c7c73891c7dfb71ddc230c48d |
| linux-kernel: Kernel | >=5.11.11 <5.12, >=5.12.0 <6.1.39, >=6.2.0 <6.3.13, >=6.4.0 <6.4.4, >=5.10.28 <5.11 | 5.12, 6.1.39, 6.3.13, 6.4.4, 5.11 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket