Critical Vulnerability in Linux Package Across Multiple Debian Versions

linux Updated 22 Oct 2026

Summary

28/05/2026
N/A
No i
Unrated
Not published

DEBIAN-CVE-2026-46160: ... Affects linux versions 5.10.103-1 – 7.1~rc5-1~exp1. 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 Linux package is a core component of the Debian operating system, providing essential functionalities for system operations, hardware management, and user interactions. It is widely used across various Debian distributions, including Bullseye, Bookworm, Trixie, and Forky. This package is crucial for maintaining system stability and performance, making it a prime target for vulnerabilities that could compromise system integrity.

Vulnerability Detail

CVE-2026-46160 is a critical vulnerability identified in the Linux package, affecting multiple Debian versions. The vulnerability originates from a flaw in the kernel that could allow an attacker to execute arbitrary code or escalate privileges, potentially leading to unauthorized access and control over the affected systems. The implications of this vulnerability are severe, as it could compromise the security of servers and workstations running Debian, exposing sensitive data and system resources to malicious actors.

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 of now, there are no specific workarounds mentioned for this vulnerability. Users are advised to apply the patch as soon as it is available to mitigate risks.

Conclusion

CVE-2026-46160 poses a significant risk to users of the Linux package across multiple Debian versions. It is essential to stay informed about this vulnerability and apply the necessary updates promptly to ensure system security. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for linux →

Share this vulnerability

FAQ

CVE-2026-46160 is a critical vulnerability in the Linux package affecting multiple Debian distributions, allowing potential unauthorized access and control.

The vulnerability affects Debian 11 (Bullseye), Debian 12 (Bookworm), Debian 13 (Trixie), and Debian 14 (Forky).

You can use Vulert, which monitors open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.

While there are no specific workarounds, it is crucial to monitor the situation and apply the update as soon as possible to mitigate risks.

Regularly check the Debian security mailing lists and use tools like Vulert to receive real-time alerts about open-source vulnerabilities.

Related vulnerabilities

Recent vulnerabilities recorded for linux.

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