CVE-2024-50165: bpf: Preserve param->string when parsing mount options
In the Linux kernel, the following vulnerability has been resolved:
bpf: Preserve param->string when parsing mount options
In bpf_parse_param(), keep the value of param->string intact so it can
be freed later. Otherwise, the kmalloc area pointed to by param->string
will be leaked as shown below:
unreferenced object 0xffff888118c46d20 (size 8):
comm "new_name", pid 12109, jiffies 4295580214
hex dump (first 8 bytes):
61 6e 79 00 38 c9 5c 7e any.8.\~
backtrace (crc e1b7f876):
[<00000000c6848ac7>] kmemleak_alloc+0x4b/0x80
[<00000000de9f7d00>] __kmalloc_node_track_caller_noprof+0x36e/0x4a0
[<000000003e29b886>] memdup_user+0x32/0xa0
[<0000000007248326>] strndup_user+0x46/0x60
[<0000000035b3dd29>] __x64_sys_fsconfig+0x368/0x3d0
[<0000000018657927>] x64_sys_call+0xff/0x9f0
[<00000000c0cabc95>] do_syscall_64+0x3b/0xc0
[<000000002f331597>] entry_SYSCALL_64_after_hwframe+0x4b/0x53
Security readout for executives and security teams
Plain-English summary
A Linux kernel bug can leak a small allocation when BPF filesystem mount options are parsed. Repeated triggering could consume kernel memory and affect availability. The supplied record rates it high severity, but does not demonstrate data theft, modification, privilege escalation, or real-world exploitation.
Executive priority
Prioritize routine expedited patching, especially for multi-user or untrusted-workload Linux hosts. This is not supported as an emergency internet-exploited issue, but a locally reachable kernel memory leak can threaten service stability. Escalate urgency if vendor guidance identifies broader impact or monitoring shows memory exhaustion.
Technical view
bpf_parse_param() overwrites or fails to preserve param->string, preventing later release of memory allocated through the fsconfig path. This is classified as CWE-401. The cited kernel commits preserve the pointer for cleanup. The supplied evidence demonstrates a kernel memory leak; it does not explain the CVSS vector’s claimed confidentiality and integrity impacts.
Likely exposure
Exposure is limited to Linux systems running releases identified as affected in the supplied record, including 6.9, 6.11.6, and 6.12. The CVSS vector indicates local access and low privileges are required. Downstream distributions may backport the fix, so version numbers alone are insufficient.
Exploitation context
CISA KEV status is false, and the supplied sources provide no evidence of active exploitation or a public exploit. The demonstrated behavior is an unreferenced kernel allocation reached through fsconfig and BPF mount-option parsing. Practical impact depends on whether an attacker can repeatedly reach that local kernel path.
Researcher notes
The record supplies CVSS 7.8 with high confidentiality, integrity, and availability impacts, yet its technical description only substantiates a small memory leak. No privilege-escalation or disclosure mechanism is provided. The affected-version representation is also incomplete or ambiguous; confirm precise branch boundaries and backports through Linux or distribution advisories.
Mitigation direction
Install a vendor-supported kernel update containing the applicable cited stable fix.
Check distribution advisories because vendors may backport fixes without changing to an upstream version.
Restrict unnecessary local account and workload access until affected systems are updated.
Prioritize shared or multi-user systems where untrusted users can exercise local kernel interfaces.
Validation and detection
Inventory running kernel versions and compare them with vendor CVE advisories.
Confirm the installed kernel changelog includes CVE-2024-50165 or an applicable cited fix commit.
Verify systems booted into the corrected kernel after updating.
Monitor kernel memory pressure and unexplained allocation growth while remediation is pending.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-401: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-401 · source CWE mapping
Missing Release of Memory after Effective Lifetime
Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.