Vulnerability in Kernel: bpf: Fix signed bounds propagation after mov32

Kernel Updated 02 Oct 2025

Summary

27/12/2021
N/A
No i
Unrated
Not published

GSD-2021-1002690: bpf: Fix signed bounds propagation after mov32. Affects Kernel versions >= 3f50f132d8400e129fc9eb68b5020167ef80a244, < e2aad0b5f2cbf71a31d00ce7bb4dee948adff5a9. 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 Kernel is a critical component of the Linux operating system that provides core functionalities and acts as a bridge between hardware and software. It manages system resources, facilitates communication between different software components, and ensures the security and stability of the system. The vulnerability in question affects the Kernel's bpf (Berkeley Packet Filter) module, which is responsible for packet filtering and network monitoring. This vulnerability can potentially lead to security breaches and unauthorized access to sensitive data.

Vulnerability Detail

The vulnerability arises from a flaw in the signed bounds propagation after mov32 operation in the bpf module of the Kernel. This flaw can be exploited by attackers to manipulate signed bounds and potentially bypass security measures. The impact and attack plausibility of this vulnerability have not been proven yet, but it is crucial to address it to prevent any potential security risks. The vulnerability was introduced in version v5.7 of the Linux Kernel and has been fixed in version v5.10.88.

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 this vulnerability has been fixed in the latest version of the Linux Kernel, there is no specific workaround available. It is advised to update the Kernel to the latest version to eliminate the vulnerability.

Conclusion

The vulnerability in the Kernel's bpf module, which allowed for signed bounds manipulation, has been addressed in version v5.10.88 of the Linux Kernel. It is crucial to update the Kernel to the latest version to ensure the security and integrity of the system. For further support and assistance with vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The impact of this vulnerability is not yet proven, but it has the potential to allow attackers to manipulate signed bounds and potentially bypass security measures.

You can use Vulert's playground at Vulert Scanner to check if your system is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities, using just a manifest file like package-lock.json.

The recommended solution is to update the Linux Kernel to version v5.10.88 or later, as this includes the necessary patch to fix the vulnerability.

As the vulnerability has been fixed in the latest version of the Linux Kernel, there is no specific workaround available. Updating the Kernel to the latest version is the best approach.

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