Action not permitted
Modal body text goes here.
Modal Title
Modal Body
EUVD-2026-364458
European Vulnerability Database identifier assigned by ENISAReserved
2026-10-02 08:32
Assigner
ENISA
Alias of
a CVE record, shown under related vulnerabilities.
This identifier carries no description, severity or references of its own:
they belong to that CVE.
{
"assigner": "ENISA",
"date_reserved": "2026-10-02T08:32:30.163980+00:00",
"id": "EUVD-2026-364458"
}
CVE-2024-50164 (GCVE-0-2024-50164)
Vulnerability from cvelistv5 – Published: 2024-11-07 09:31 – Updated: 2026-09-08 08:39
VLAI
EPSS
VEX
Title
bpf: Fix overloading of MEM_UNINIT's meaning
Summary
In the Linux kernel, the following vulnerability has been resolved:
bpf: Fix overloading of MEM_UNINIT's meaning
Lonial reported an issue in the BPF verifier where check_mem_size_reg()
has the following code:
if (!tnum_is_const(reg->var_off))
/* For unprivileged variable accesses, disable raw
* mode so that the program is required to
* initialize all the memory that the helper could
* just partially fill up.
*/
meta = NULL;
This means that writes are not checked when the register containing the
size of the passed buffer has not a fixed size. Through this bug, a BPF
program can write to a map which is marked as read-only, for example,
.rodata global maps.
The problem is that MEM_UNINIT's initial meaning that "the passed buffer
to the BPF helper does not need to be initialized" which was added back
in commit 435faee1aae9 ("bpf, verifier: add ARG_PTR_TO_RAW_STACK type")
got overloaded over time with "the passed buffer is being written to".
The problem however is that checks such as the above which were added later
via 06c1c049721a ("bpf: allow helpers access to variable memory") set meta
to NULL in order force the user to always initialize the passed buffer to
the helper. Due to the current double meaning of MEM_UNINIT, this bypasses
verifier write checks to the memory (not boundary checks though) and only
assumes the latter memory is read instead.
Fix this by reverting MEM_UNINIT back to its original meaning, and having
MEM_WRITE as an annotation to BPF helpers in order to then trigger the
BPF verifier checks for writing to memory.
Some notes: check_arg_pair_ok() ensures that for ARG_CONST_SIZE{,_OR_ZERO}
we can access fn->arg_type[arg - 1] since it must contain a preceding
ARG_PTR_TO_MEM. For check_mem_reg() the meta argument can be removed
altogether since we do check both BPF_READ and BPF_WRITE. Same for the
equivalent check_kfunc_mem_size_reg().
Severity
7.8 (High)
Assigner
References
6 references
Impacted products
5 products
| Vendor | Product | Version | |
|---|---|---|---|
| Linux | Linux |
Affected:
97e6d7dab1ca4648821c790a2b7913d6d5d549db , < 43f4df339a4d375bedcad29a61ae6f0ee7a048f8
(git)
Affected: 97e6d7dab1ca4648821c790a2b7913d6d5d549db , < 48068ccaea957469f1adf78dfd2c1c9a7e18f0fe (git) Affected: 97e6d7dab1ca4648821c790a2b7913d6d5d549db , < 54bc31682660810af1bed7ca7a19f182df8d3df8 (git) Affected: 97e6d7dab1ca4648821c790a2b7913d6d5d549db , < 8ea607330a39184f51737c6ae706db7fdca7628e (git) Affected: 6099a6c8a749a5c8d5f8b4c4342022a92072a02b (git) Affected: bfe25df63048edd4ceaf78a2fc755d5e2befc978 (git) Affected: 717c39718dbc4f7ebcbb7b625fb11851cd9007fe (git) Affected: 5d0bba8232bf22ce13747cbfc8f696318ff01a50 (git) Affected: 70674d11d14eeecad90be4b409a22b902112ba32 (git) Affected: a08d942ecbf46e23a192093f6983cb1d779f4fa8 (git) Affected: 5.15.45 , < 5.16 (semver) Affected: 5.17.13 , < 5.18 (semver) Affected: 5.18.2 , < 5.19 (semver) |
|
| Linux | Linux |
Affected:
5.19
Unaffected: 0 , < 5.19 (semver) Unaffected: 6.1.125 , ≤ 6.1.* (semver) Unaffected: 6.6.59 , ≤ 6.6.* (semver) Unaffected: 6.11.6 , ≤ 6.11.* (semver) Unaffected: 6.12 , ≤ * (original_commit_for_fix) |
|
| Siemens | SIMATIC S7-1500 CPU 1518-4 PN/DP MFP |
Affected:
V3.1.6 , < *
(custom)
|
|
| Siemens | SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP |
Affected:
V3.1.6 , < *
(custom)
|
|
| Siemens | SIPLUS S7-1500 CPU 1518-4 PN/DP MFP |
Affected:
V3.1.6 , < *
(custom)
|
{
"containers": {
"adp": [
{
"providerMetadata": {
"dateUpdated": "2025-11-03T20:43:57.432Z",
"orgId": "af854a3a-2127-422b-91ae-364da2661108",
"shortName": "CVE"
},
"references": [
{
"url": "https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html"
}
],
"title": "CVE Program Container"
},
{
"affected": [
{
"defaultStatus": "unknown",
"product": "SIMATIC S7-1500 CPU 1518-4 PN/DP MFP",
"vendor": "Siemens",
"versions": [
{
"lessThan": "*",
"status": "affected",
"version": "V3.1.6",
"versionType": "custom"
}
]
},
{
"defaultStatus": "unknown",
"product": "SIMATIC S7-1500 CPU 1518-4 PN/DP MFP",
"vendor": "Siemens",
"versions": [
{
"lessThan": "*",
"status": "affected",
"version": "V3.1.6",
"versionType": "custom"
}
]
},
{
"defaultStatus": "unknown",
"product": "SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP",
"vendor": "Siemens",
"versions": [
{
"lessThan": "*",
"status": "affected",
"version": "V3.1.6",
"versionType": "custom"
}
]
},
{
"defaultStatus": "unknown",
"product": "SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP",
"vendor": "Siemens",
"versions": [
{
"lessThan": "*",
"status": "affected",
"version": "V3.1.6",
"versionType": "custom"
}
]
},
{
"defaultStatus": "unknown",
"product": "SIPLUS S7-1500 CPU 1518-4 PN/DP MFP",
"vendor": "Siemens",
"versions": [
{
"lessThan": "*",
"status": "affected",
"version": "V3.1.6",
"versionType": "custom"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-09-08T08:39:27.274Z",
"orgId": "0b142b55-0307-4c5a-b3c9-f314f3fb7c5e",
"shortName": "siemens-SADP"
},
"references": [
{
"url": "https://cert-portal.siemens.com/productcert/html/ssa-019113.html"
}
],
"x_adpType": "supplier"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"kernel/bpf/verifier.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "43f4df339a4d375bedcad29a61ae6f0ee7a048f8",
"status": "affected",
"version": "97e6d7dab1ca4648821c790a2b7913d6d5d549db",
"versionType": "git"
},
{
"lessThan": "48068ccaea957469f1adf78dfd2c1c9a7e18f0fe",
"status": "affected",
"version": "97e6d7dab1ca4648821c790a2b7913d6d5d549db",
"versionType": "git"
},
{
"lessThan": "54bc31682660810af1bed7ca7a19f182df8d3df8",
"status": "affected",
"version": "97e6d7dab1ca4648821c790a2b7913d6d5d549db",
"versionType": "git"
},
{
"lessThan": "8ea607330a39184f51737c6ae706db7fdca7628e",
"status": "affected",
"version": "97e6d7dab1ca4648821c790a2b7913d6d5d549db",
"versionType": "git"
},
{
"status": "affected",
"version": "6099a6c8a749a5c8d5f8b4c4342022a92072a02b",
"versionType": "git"
},
{
"status": "affected",
"version": "bfe25df63048edd4ceaf78a2fc755d5e2befc978",
"versionType": "git"
},
{
"status": "affected",
"version": "717c39718dbc4f7ebcbb7b625fb11851cd9007fe",
"versionType": "git"
},
{
"status": "affected",
"version": "5d0bba8232bf22ce13747cbfc8f696318ff01a50",
"versionType": "git"
},
{
"status": "affected",
"version": "70674d11d14eeecad90be4b409a22b902112ba32",
"versionType": "git"
},
{
"status": "affected",
"version": "a08d942ecbf46e23a192093f6983cb1d779f4fa8",
"versionType": "git"
},
{
"lessThan": "5.16",
"status": "affected",
"version": "5.15.45",
"versionType": "semver"
},
{
"lessThan": "5.18",
"status": "affected",
"version": "5.17.13",
"versionType": "semver"
},
{
"lessThan": "5.19",
"status": "affected",
"version": "5.18.2",
"versionType": "semver"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"kernel/bpf/verifier.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "5.19"
},
{
"lessThan": "5.19",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.1.*",
"status": "unaffected",
"version": "6.1.125",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.59",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.11.*",
"status": "unaffected",
"version": "6.11.6",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "6.12",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.1.125",
"versionStartIncluding": "5.19",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.6.59",
"versionStartIncluding": "5.19",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.11.6",
"versionStartIncluding": "5.19",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12",
"versionStartIncluding": "5.19",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "5.15.45",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "5.17.13",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "5.18.2",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "5.15.45",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "5.17.13",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "5.18.2",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix overloading of MEM_UNINIT\u0027s meaning\n\nLonial reported an issue in the BPF verifier where check_mem_size_reg()\nhas the following code:\n\n if (!tnum_is_const(reg-\u003evar_off))\n /* For unprivileged variable accesses, disable raw\n * mode so that the program is required to\n * initialize all the memory that the helper could\n * just partially fill up.\n */\n meta = NULL;\n\nThis means that writes are not checked when the register containing the\nsize of the passed buffer has not a fixed size. Through this bug, a BPF\nprogram can write to a map which is marked as read-only, for example,\n.rodata global maps.\n\nThe problem is that MEM_UNINIT\u0027s initial meaning that \"the passed buffer\nto the BPF helper does not need to be initialized\" which was added back\nin commit 435faee1aae9 (\"bpf, verifier: add ARG_PTR_TO_RAW_STACK type\")\ngot overloaded over time with \"the passed buffer is being written to\".\n\nThe problem however is that checks such as the above which were added later\nvia 06c1c049721a (\"bpf: allow helpers access to variable memory\") set meta\nto NULL in order force the user to always initialize the passed buffer to\nthe helper. Due to the current double meaning of MEM_UNINIT, this bypasses\nverifier write checks to the memory (not boundary checks though) and only\nassumes the latter memory is read instead.\n\nFix this by reverting MEM_UNINIT back to its original meaning, and having\nMEM_WRITE as an annotation to BPF helpers in order to then trigger the\nBPF verifier checks for writing to memory.\n\nSome notes: check_arg_pair_ok() ensures that for ARG_CONST_SIZE{,_OR_ZERO}\nwe can access fn-\u003earg_type[arg - 1] since it must contain a preceding\nARG_PTR_TO_MEM. For check_mem_reg() the meta argument can be removed\naltogether since we do check both BPF_READ and BPF_WRITE. Same for the\nequivalent check_kfunc_mem_size_reg()."
}
],
"metrics": [
{
"cvssV3_1": {
"baseScore": 7.8,
"baseSeverity": "HIGH",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"scenarios": [
{
"lang": "en",
"value": "AV:L - The vulnerability is reached through the bpf(2) syscall (BPF_MAP_CREATE/BPF_MAP_FREEZE/BPF_PROG_LOAD) by a process on the local system. Per kernel scoring guidance, BPF verifier bugs are Local.\nAC:L - The attacker fully authors the BPF program and the map contents; passing a non-constant size register to a helper such as bpf_skb_load_bytes() deterministically bypasses the write check every time. No race, timing window, or uncontrolled memory layout is involved.\nPR:L - An unprivileged local user can load a BPF_PROG_TYPE_SOCKET_FILTER program reaching bpf_skb_load_bytes() when kernel.unprivileged_bpf_disabled=0 (default on kernels without CONFIG_BPF_UNPRIV_DEFAULT_OFF, e.g. Android and many embedded builds), and CAP_BPF is delegable into unprivileged user namespaces via BPF tokens (bpf_token_capable() uses ns_capable). No real root in the init namespace is needed.\nUI:N - The attacker performs every step itself \u2014 creating and freezing the map, loading the program, and triggering it (e.g. by sending a packet to its own socket). No other user\u0027s action is required.\nS:U - The verifier bypass and its impact are both within the kernel\u0027s own security authority; this is a standard local privilege escalation with no VM, IOMMU, or hypervisor boundary crossed.\nC:H - Writing to a frozen BPF_F_RDONLY_PROG map desynchronizes the values the verifier constant-folded via bpf_map_direct_read()/__mark_reg_known() from the values used at runtime, so bounds the verifier proved safe become arbitrarily out-of-bounds, yielding an arbitrary kernel memory read primitive.\nI:H - The bug directly permits a BPF program to write into memory the verifier guarantees is immutable (.rodata global maps, PTR_TO_MAP_KEY, read-only PTR_TO_MEM/PTR_TO_BUF, and program context), and the resulting verifier invariant break escalates to an arbitrary kernel write and full privilege escalation.\nA:H - Out-of-bounds kernel reads and writes resulting from the broken verifier bounds reasoning readily corrupt kernel memory and panic the system, and the attacker can trigger this repeatedly."
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-08-05T11:42:12.665Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/43f4df339a4d375bedcad29a61ae6f0ee7a048f8"
},
{
"url": "https://git.kernel.org/stable/c/48068ccaea957469f1adf78dfd2c1c9a7e18f0fe"
},
{
"url": "https://git.kernel.org/stable/c/54bc31682660810af1bed7ca7a19f182df8d3df8"
},
{
"url": "https://git.kernel.org/stable/c/8ea607330a39184f51737c6ae706db7fdca7628e"
}
],
"title": "bpf: Fix overloading of MEM_UNINIT\u0027s meaning",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2024-50164",
"datePublished": "2024-11-07T09:31:41.012Z",
"dateReserved": "2024-10-21T19:36:19.962Z",
"dateUpdated": "2026-09-08T08:39:27.274Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
Loading…
Trend slope:
-
(linear fit over daily sighting counts)
Show additional events:
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.
Loading…
Loading…