Vulnerability in Kernel: gcc-plugins/stackleak

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1001164: gcc-plugins/stackleak: Exactly match strings instead of prefixes. Affects Kernel versions < 0a639f01f90dea71462320d2e477d716a2479a61. 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 Your last release was probably never penetration tested 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 functionality and acts as an interface between hardware and software. It manages system resources, facilitates communication between different software components, and ensures the security and stability of the system. The gcc-plugins/stackleak is a plugin for the GNU Compiler Collection (GCC) that enhances the kernel's stack protection mechanisms by detecting stack overflows. This vulnerability in gcc-plugins/stackleak allows for potential security breaches and unauthorized access to sensitive data.

Vulnerability Detail

The vulnerability in gcc-plugins/stackleak arises from the improper matching of strings. Instead of exactly matching strings, the plugin uses string prefixes, which can lead to false positives and false negatives in stack leak detection. This flaw could be exploited by attackers to bypass stack protection mechanisms and execute arbitrary code on the system. The impact and attack plausibility of this vulnerability have not been proven yet. It is important to note that this vulnerability has been fixed in Linux Kernel version v5.17.2 by commit 0a639f01f90dea71462320d2e477d716a2479a61.

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

There is no specific workaround mentioned for this vulnerability. It is advised to follow the recommended fix by updating the Linux Kernel to the latest version.

Conclusion

In conclusion, the vulnerability in gcc-plugins/stackleak in the Kernel could allow attackers to bypass stack protection mechanisms and execute arbitrary code on the system. It is crucial to update the Linux Kernel to version v5.17.2 or later to mitigate this vulnerability. Regularly checking for and applying security patches is essential to ensure the security and stability of the system. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

This vulnerability in gcc-plugins/stackleak could potentially allow attackers to bypass stack protection mechanisms and execute arbitrary code on the system, leading to unauthorized access to sensitive data and potential system compromise.

You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and the Vulert Playground will analyze it for any open-source vulnerabilities, including this one.

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

The exact attack vectors and remote exploitability of this vulnerability have not been proven yet. However, it is always recommended to keep systems up to date with the latest security patches to minimize the risk of remote exploitation.

The primary mitigation for this vulnerability is to update the Linux Kernel to version v5.17.2 or later. Additionally, it is good security practice to follow best coding practices, perform regular security audits, and implement defense-in-depth strategies to minimize the impact of potential vulnerabilities.

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