Memory Leak Vulnerability in samples/landlock

Kernel Updated 02 Oct 2025

Summary

24/04/2022
N/A
No i
Unrated
Not published

GSD-2022-1001288: samples/landlock: Fix path_list memory leak. Affects Kernel versions < 017196730299ccd6eed24bbfabed8af4ffd81530. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The samples/landlock is a component of the Linux Kernel, which is responsible for providing a sandboxing mechanism for restricting access to certain resources by user-space processes. It allows fine-grained control over file system operations, network access, and other system resources. However, a memory leak vulnerability has been identified in the path_list implementation of samples/landlock.

Vulnerability Detail

The memory leak vulnerability in samples/landlock occurs due to improper memory management in the path_list feature. When adding paths to the list, memory is allocated but not properly freed, leading to a continuous consumption of memory resources. An attacker could potentially exploit this vulnerability by repeatedly adding paths to exhaust system memory, resulting in a denial-of-service condition or other adverse effects.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a workaround, users can avoid using the path_list feature in samples/landlock until the kernel is updated to the fixed version. By refraining from adding paths to the list, the memory leak vulnerability can be mitigated.

Conclusion

The memory leak vulnerability in samples/landlock can be addressed by updating the Linux Kernel to version v5.17.2 or later. Until the update is applied, users can mitigate the risk by avoiding the use of the path_list feature. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

samples/landlock is a component of the Linux Kernel that provides sandboxing capabilities for restricting access to system resources by user-space processes.

The memory leak vulnerability in samples/landlock can lead to a continuous consumption of memory resources, potentially resulting in a denial-of-service condition or other adverse effects.

To fix this vulnerability, update the Linux Kernel to version v5.17.2 or later, which includes the necessary fix for the memory leak in samples/landlock.

Yes, users can avoid using the path_list feature in samples/landlock until the kernel is updated to the fixed version. By refraining from adding paths to the list, the memory leak vulnerability can be mitigated.

For more details about this vulnerability, refer to the provided references link in the vulnerability details section.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback