CVE-2024-47728

published 21 Oct 2024 · updated 7 Aug 2026

bpf: Zero former ARG_PTR_TO_{LONG,INT} args in case of error

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 4b3786a6c5397dc220b1483d8e2f4867743e966f, Kernel 594a9f5a8d2de2573a856e506f77ba7dd2cefc6a, Kernel 599d15b6d03356a97bff7a76155c5604c42a2962 and 2 more.

In the Linux kernel, the following vulnerability has been resolved: bpf: Zero former ARG_PTR_TO_{LONG,INT} args in case of error For all non-tracing helpers which formerly had ARG_PTR_TO_{LONG,INT} as input arguments, zero the value for the case of an error as otherwise it could leak memory. For tracing, it is not needed given CAP_PERFMON can already read all kernel memory anyway hence bpf_get_func_arg() and bpf_get_func_ret() is skipped in here. Also, the MTU helpers mtu_len pointer value is being written but also read. Technically, the MEM_UNINIT should not be there in order to always force init. Removing MEM_UNINIT needs more verifier rework though: MEM_UNINIT right now implies two things actually: i) write into memory, ii) memory does not have to be initialized. If we lift MEM_UNINIT, it then becomes: i) read into memory, ii) memory must be initialized. This means that for bpf_*_check_mtu() we're readding the issue we're trying to fix, that is, it would then be able to write back into things like .rodata BPF maps. Follow-up work will rework the MEM_UNINIT semantics such that the intent can be better expressed. For now just clear the *mtu_len on error path which can be lifted later again.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=5.2, >=d7a4cb9b6705a89937d12c8158a35a3145dc967a <4b3786a6c5397dc220b1483d8e2f4867743e966f, >=d7a4cb9b6705a89937d12c8158a35a3145dc967a <594a9f5a8d2de2573a856e506f77ba7dd2cefc6a, >=d7a4cb9b6705a89937d12c8158a35a3145dc967a <599d15b6d03356a97bff7a76155c5604c42a2962, >=d7a4cb9b6705a89937d12c8158a35a3145dc967a <8397bf78988f3ae9dbebb0200189a62a57264980, >=d7a4cb9b6705a89937d12c8158a35a3145dc967a <a634fa8e480ac2423f86311a602f6295df2c8ed04b3786a6c5397dc220b1483d8e2f4867743e966f, 594a9f5a8d2de2573a856e506f77ba7dd2cefc6a, 599d15b6d03356a97bff7a76155c5604c42a2962, 8397bf78988f3ae9dbebb0200189a62a57264980, a634fa8e480ac2423f86311a602f6295df2c8ed0

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2024-47728 severity on Zeptric[![CVE-2024-47728](https://zeptric.io/badge/cve/CVE-2024-47728.svg)](https://zeptric.io/cve/CVE-2024-47728)