Stack Information Leak in ipoctal Package

Kernel Updated 02 Oct 2025

Summary

19/10/2021
N/A
No i
Unrated
Not published

GSD-2021-1001555: ipack: ipoctal: fix stack information leak. Affects Kernel versions >= ba4dc61fe8c545a5d6a68b63616776556b771f51, < 829f13d6079cf7a2465522f39acb43033e9b320d. 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 ipoctal package is a component of the Linux Kernel, which is responsible for managing network interfaces and communication protocols. It provides functionality for handling IP packets and octal data representation. The vulnerability in the ipoctal package allows for a stack information leak, potentially exposing sensitive data stored in the stack memory.

Vulnerability Detail

The vulnerability in the ipoctal package arises from a flaw in the implementation that allows an attacker to leak stack information. By exploiting this vulnerability, an attacker could gain access to sensitive data stored in the stack memory, such as cryptographic keys, passwords, or other confidential information. This information leak could lead to further attacks or unauthorized access to the system.

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 apply the patch provided in the commit 829f13d6079cf7a2465522f39acb43033e9b320d. The patch can be manually applied to the affected system by following the instructions provided in the commit. However, it is strongly recommended to update to the latest version of the Linux Kernel to ensure comprehensive security fixes.

Conclusion

The stack information leak vulnerability in the ipoctal package of the Linux Kernel can lead to the exposure of sensitive data stored in the stack memory. It is crucial to update the Linux Kernel to the latest version or apply the provided patch to mitigate this vulnerability. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

This vulnerability allows an attacker to leak stack information, potentially exposing sensitive data stored in the stack memory. The leaked information could be used for further attacks or unauthorized access to the system.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your manifest file (e.g., package-lock.json) to the playground, and it will analyze and alert you if the vulnerability is present.

At the time of this report, there is no known public exploit for this vulnerability. However, it is crucial to apply the recommended fixes to mitigate the risk.

To exploit this vulnerability, an attacker would need to have access to the affected system and the capability to execute malicious code.

No, this vulnerability requires local access to the affected system to exploit it.

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