In the Linux kernel, the following vulnerability has been resolved:
samples/landlock: Fix path_list memory leak
Clang static analysis reports this error
sandboxer.c:134:8: warning: Potential leak of memory
pointed to by 'path_list'
ret = 0;
^
path_list is allocated in parse_path() but never freed.
Security readout for executives and security teams
Plain-English summary
This CVE is a memory leak in the Linux kernel Landlock sample sandboxer code. A local low-privileged user could trigger resource exhaustion if the vulnerable sample program is built and used. The business risk is availability disruption, not data theft or integrity compromise, based on the supplied CVSS vector.
Executive priority
Treat as a moderate availability issue. It is not evidenced as remotely exploitable or actively exploited, but systems exposing local access should validate patch status during normal kernel maintenance.
Technical view
The issue is CWE-401 in samples/landlock sandboxer.c. parse_path() allocates path_list, but an error path sets ret to 0 without freeing it. The supplied CVSS vector is local, low complexity, low privileges, no user interaction, unchanged scope, and high availability impact.
Likely exposure
Exposure appears limited to Linux environments carrying the affected samples/landlock code and actually building or using the sandboxer sample. The bundle does not show remote exposure, confidentiality impact, integrity impact, or broad default-service exposure.
Exploitation context
The source bundle does not show active exploitation, proof-of-concept activity, or CISA KEV listing. Any exploitation would require local access with low privileges and would target availability through memory leakage, not direct privilege escalation.
Researcher notes
The evidence is narrow: a Clang static analysis finding and stable Linux fix references. The record names samples/landlock, so avoid expanding scope to unrelated Landlock enforcement paths without vendor confirmation.
Mitigation direction
Review vendor kernel guidance for the applicable fixed release or backport.
Apply the referenced Linux stable fixes where the sample is present or used.
Avoid deploying or running the vulnerable Landlock sample sandboxer in production workflows.
Track distribution advisories for packaged kernel or sample-code backports.
Validation and detection
Inventory Linux kernel versions and distribution backport status.
Check whether samples/landlock sandboxer is built, shipped, or used locally.
Confirm the relevant stable fix commit is present in source or vendor patches.
Prioritize validation on systems allowing local untrusted shell access.
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.