CVE-2024-47728bpf: Zero former ARG_PTR_TO_{LONG,INT} args in case of error
- 5.5MediumCVSS base score
- 0.24%Exploitation in 30 daysEPSS · top 85% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
- 21 days later
· 21 days later
Published
- 19 months later
· 19 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.24% · top 85% of all CVEs (12 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected d7a4cb9b6705a89937d12c8158a35a3145dc967a – < 8397bf78988f3ae9dbebb0200189a62a57264980
- affected d7a4cb9b6705a89937d12c8158a35a3145dc967a – < a634fa8e480ac2423f86311a602f6295df2c8ed0
- affected d7a4cb9b6705a89937d12c8158a35a3145dc967a – < 599d15b6d03356a97bff7a76155c5604c42a2962
- affected d7a4cb9b6705a89937d12c8158a35a3145dc967a – < 594a9f5a8d2de2573a856e506f77ba7dd2cefc6a
- affected d7a4cb9b6705a89937d12c8158a35a3145dc967a – < 4b3786a6c5397dc220b1483d8e2f4867743e966f
- affected 5.2
- unaffected < 5.2
- unaffected 6.1.113 – ≤ 6.1.*
- unaffected 6.6.54 – ≤ 6.6.*
- unaffected 6.10.13 – ≤ 6.10.*
- unaffected 6.11.2 – ≤ 6.11.*
- unaffected 6.12 – ≤ *
References
References6
- https://git.kernel.org/stable/c/8397bf78988f3ae9dbebb0200189a62a57264980 (opens in a new tab)
- https://git.kernel.org/stable/c/a634fa8e480ac2423f86311a602f6295df2c8ed0 (opens in a new tab)
- https://git.kernel.org/stable/c/599d15b6d03356a97bff7a76155c5604c42a2962 (opens in a new tab)
- https://git.kernel.org/stable/c/594a9f5a8d2de2573a856e506f77ba7dd2cefc6a (opens in a new tab)
- https://git.kernel.org/stable/c/4b3786a6c5397dc220b1483d8e2f4867743e966f (opens in a new tab)
- https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2024-42647 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2024-47728)Record last updated .