Missing Bit in panic_print Function in Linux Kernel

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1001747: docs: sysctl/kernel: add missing bit to panic_print. Affects Kernel versions >= de6da1e8bcf0dd2058b950b127491821207679dc, < 3fc38521fc3007af03c606d37997cbb75caa4361. 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 Linux Kernel is the core component of the Linux operating system. It provides essential functionality and interfaces for various hardware and software components. The panic_print function is responsible for printing kernel panic messages when the system encounters critical errors. However, a missing bit in the sysctl/kernel configuration can lead to incomplete panic messages being printed, potentially hindering the troubleshooting and analysis of system failures.

Vulnerability Detail

The vulnerability arises from a missing bit in the sysctl/kernel configuration related to the panic_print function. When this bit is not set correctly, the kernel may fail to print complete panic messages during critical errors. This can make it challenging to diagnose and resolve system failures, potentially leading to extended downtime and difficulty in identifying the root cause of the issues. Attackers may also exploit this vulnerability to obfuscate their activities and evade detection.

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

If updating the Linux Kernel is not immediately feasible, a temporary workaround can be implemented by manually modifying the sysctl/kernel configuration to include the missing bit. The specific steps to apply this workaround may vary depending on the Linux distribution and version. It is recommended to consult the official documentation or seek assistance from the Linux distribution's support channels for guidance on modifying the sysctl/kernel configuration.

Conclusion

The missing bit in the sysctl/kernel configuration related to the panic_print function in the Linux Kernel can lead to incomplete panic messages being printed during critical errors. This vulnerability can hinder troubleshooting efforts and make it difficult to identify the root cause of system failures. It is crucial to update the Linux Kernel to version v5.15.33 or later to fix this issue. In the meantime, a temporary workaround can be applied by modifying the sysctl/kernel configuration. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability can result in incomplete panic messages being printed during critical errors in the Linux Kernel. This can hinder the troubleshooting and analysis of system failures, potentially leading to extended downtime and difficulty in identifying the root cause of the issues.

Attackers can leverage this vulnerability to obfuscate their activities and evade detection. By manipulating the sysctl/kernel configuration, they can prevent complete panic messages from being printed, making it harder for system administrators to identify and respond to critical errors.

The vulnerability was introduced in Linux Kernel version v5.2 by commit de6da1e8bcf0dd2058b950b127491821207679dc. It is present in all versions between v5.2 and v5.15.32 (inclusive). The issue is resolved in version v5.15.33 and later.

Yes, the vulnerability is fixed in Linux Kernel version v5.15.33. Users are advised to update their kernel to this version or a later one to mitigate the issue.

If immediate kernel update is not feasible, a temporary workaround involves manually modifying the sysctl/kernel configuration to include the missing bit. However, it is recommended to update to the fixed kernel version as soon as possible.

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