Excessive Memory Allocation Vulnerability in bpf

Kernel Updated 02 Oct 2025

Summary

28/06/2022
N/A
No i
Unrated
Not published

GSD-2022-1003170: bpf: Fix excessive memory allocation in stack_map_alloc(). Affects Kernel versions >= b936ca643ade11f265fa10e5fb71c20d9c5243f1, < b9037efc1f3483cfa459e59f803989a6cee4a8da. 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 bpf package is a component of the Linux Kernel, which is responsible for implementing Berkeley Packet Filters (BPF). BPF provides a framework for executing custom programs within the kernel, allowing for efficient packet filtering and network monitoring. This vulnerability affects versions of the Linux Kernel from v5.3 to v5.17.12.

Vulnerability Detail

The vulnerability, identified as GSD-2022-1003170, is related to excessive memory allocation in the stack_map_alloc() function of the bpf package. This flaw could potentially be exploited by an attacker to cause a denial-of-service (DoS) condition or execute arbitrary code with elevated privileges. The vulnerability was introduced in Linux Kernel v5.3 and has been fixed in v5.17.13.

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

No specific workaround has been provided for this vulnerability.

Conclusion

In conclusion, the excessive memory allocation vulnerability in the bpf package of the Linux Kernel can potentially lead to a DoS condition or arbitrary code execution. It is crucial to update the Linux Kernel to version v5.17.13 or later to mitigate this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

This vulnerability could potentially lead to a denial-of-service (DoS) condition or allow an attacker to execute arbitrary code with elevated privileges.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and it will provide real-time alerts for open-source vulnerabilities.

At the time of this report, there is no known exploit for this vulnerability. However, it is important to apply the recommended fix to mitigate any potential risks.

This vulnerability specifically affects the bpf package in the Linux Kernel. However, it is always recommended to keep all software components up to date to ensure overall system security.

You can find more information about this vulnerability in the GSD-2022-1003170 JSON file available on the GitHub repository of the Cloud Security Alliance's GSD Database (https://github.com/cloudsecurityalliance/gsd-database).

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