CVE-2024-47728: Linux kernel · bpf: Zero former ARG_PTR_TO_{LONG,INT} args in case of error
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 5.5 Medium · fixed in 6.8.0-1023.25~22.04.1 : update Linux kernel when convenient.
Data as of 28 Oct 2026, 11:13 UTC
- Patch
- Available – fixed in 6.8.0-1023.25~22.04.1, 6.8.0-1025.30~22.04.1, 6.8.0-1024.26~22.04.1 +29
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 21 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-7276-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7277-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7301-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7303-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7304-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7303-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7310-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7311-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7303-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7384-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7385-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7386-1 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-6.11pkg:deb/ubuntu/linux-azure-6.11?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-nvidiapkg:deb/ubuntu/linux-azure-nvidia?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
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.
References
- ubuntu.com/security/CVE-2024-47728 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2024-47728 (opens in a new tab)
- git.kernel.org/linus/4b3786a6c5397dc220b1483d8e2f4867743e966f (opens in a new tab)
- git.kernel.org/stable/c/8397bf78988f3ae9dbebb0200189a62a57264980 (opens in a new tab)
- git.kernel.org/stable/c/a634fa8e480ac2423f86311a602f6295df2c8ed0 (opens in a new tab)
- git.kernel.org/stable/c/599d15b6d03356a97bff7a76155c5604c42a2962 (opens in a new tab)
- git.kernel.org/stable/c/594a9f5a8d2de2573a856e506f77ba7dd2cefc6a (opens in a new tab)
- git.kernel.org/stable/c/4b3786a6c5397dc220b1483d8e2f4867743e966f (opens in a new tab)
- ubuntu.com/security/notices/USN-7276-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7277-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7301-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7303-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7304-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7303-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7310-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7311-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7303-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7384-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7385-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7386-1 (opens in a new tab)