bpf: Zero former ARG_PTR_TO_{LONG,INT} args in case of error
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.1.113, 6.10.13, 6.11.2, 6.6.54
- CVEs
- CVE-2024-47728
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 07:12 UTC · Revision 1
Source evidence
bpf: Zero former ARG_PTR_TO_{LONG,INT} args in case of error
core-osv · Original sourcePublished 21 Oct 2024, 12:14 UTC
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.
osv:CVE-2024-47728
Kernel
Fixed versions: 6.1.113, 6.6.54, 6.10.13, 6.11.2
Complete source record
{
"id": "386c8bd46f58fd39f852af0ba3b36c59e83552f39b49af4a09b638369af6bb59",
"url": "https://osv.dev/vulnerability/CVE-2024-47728",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "bpf: Zero former ARG_PTR_TO_{LONG,INT} args in case of error",
"summary": "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.",
"evidence": "osv:CVE-2024-47728",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.1.113",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.54",
"evidence": "/affected/1/ranges"
},
{
"value": "6.10.13",
"evidence": "/affected/1/ranges"
},
{
"value": "6.11.2",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2024-47728",
"aliases": [
"CVE-2024-47728"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "d7a4cb9b6705a89937d12c8158a35a3145dc967a"
},
{
"fixed": "8397bf78988f3ae9dbebb0200189a62a57264980"
},
{
"fixed": "a634fa8e480ac2423f86311a602f6295df2c8ed0"
},
{
"fixed": "599d15b6d03356a97bff7a76155c5604c42a2962"
},
{
"fixed": "594a9f5a8d2de2573a856e506f77ba7dd2cefc6a"
},
{
"fixed": "4b3786a6c5397dc220b1483d8e2f4867743e966f"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-47728.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.2.0"
},
{
"fixed": "6.1.113"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.54"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.10.13"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.11.0"
},
{
"fixed": "6.11.2"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-47728.json"
}
}
],
"modified": "2026-10-28T02:30:26.636899613Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/4b3786a6c5397dc220b1483d8e2f4867743e966f",
"https://git.kernel.org/stable/c/594a9f5a8d2de2573a856e506f77ba7dd2cefc6a",
"https://git.kernel.org/stable/c/599d15b6d03356a97bff7a76155c5604c42a2962",
"https://git.kernel.org/stable/c/8397bf78988f3ae9dbebb0200189a62a57264980",
"https://git.kernel.org/stable/c/a634fa8e480ac2423f86311a602f6295df2c8ed0",
"https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/47xxx/CVE-2024-47728.json",
"https://nvd.nist.gov/vuln/detail/CVE-2024-47728",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/47xxx/CVE-2024-47728.json"
}
},
"related_cves": [
{
"value": "CVE-2024-47728",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 493170,
"published_at": "2024-10-21T12:14:01.012+00:00"
}