Critical Vulnerability in Linux Package Affecting Debian Versions

linux Updated 22 Oct 2026

Summary

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

DEBIAN-CVE-2026-46197: ... 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 managing system resources and hardware interactions. It is widely used across various Debian distributions, including Bullseye, Bookworm, Trixie, and Forky. This package is crucial for system stability and performance, making its security paramount.

Vulnerability Detail

CVE-2026-46197 is a critical vulnerability identified in the Linux package that affects multiple Debian versions. The vulnerability originates from improper handling of certain system calls, which could allow an attacker to execute arbitrary code with elevated privileges. This could lead to unauthorized access to sensitive data, system compromise, or denial of service. The vulnerability is particularly concerning as it affects all versions of the Linux package prior to the fixed versions.

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 temporary workaround, users can limit access to the affected system or disable certain functionalities that rely on the vulnerable system calls until the package is updated. However, this is not a permanent solution and updating the package is strongly recommended.

Conclusion

CVE-2026-46197 poses a significant risk to users of the Linux package across various Debian distributions. It is crucial to update to the patched versions to mitigate potential security threats. Users are encouraged to monitor their systems and utilize tools like Vulert for ongoing vulnerability management.

See every vulnerability recorded for linux →

Share this vulnerability

FAQ

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

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

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

If immediate updates are not possible, consider limiting access to the affected system and disabling functionalities that rely on the vulnerable system calls as a temporary measure.

Yes, the permanent fix is to update the Linux package to the specified patched versions for your Debian distribution.

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