DSA Master Device Unbind Panic in Linux Kernel

Kernel Updated 02 Oct 2025

Summary

27/02/2022
N/A
No i
Unrated
Not published

GSD-2022-1000519: net: dsa: fix panic when DSA master device unbinds on shutdown. Affects Kernel versions >= 0650bf52b31ff35dc6430fc2e37969c36baba724, < 89b60402d43cdab4387dbbf24afebda5cf092ae7. 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 Kernel is the core component of the Linux operating system, responsible for managing system resources and providing essential functionality. The DSA (Distributed Switch Architecture) subsystem in the Linux Kernel enables the use of distributed switches, allowing network traffic to be distributed across multiple physical devices. The DSA master device is a key component of this subsystem, responsible for managing and controlling the distributed switches. However, a vulnerability has been discovered in the DSA master device that can lead to a panic when the device is unbound during system shutdown.

Vulnerability Detail

The vulnerability arises when the DSA master device is unbound during system shutdown. This can trigger a panic, causing the system to crash. The exact impact and attack vectors of this vulnerability have not been proven, but it has the potential to disrupt network connectivity and compromise system stability. The vulnerability was introduced in Linux Kernel version 5.15 and has been fixed in version 5.16.10.

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 known workaround for this vulnerability. It is necessary to apply the fix by updating the Linux Kernel.

Conclusion

The DSA master device unbind panic vulnerability in the Linux Kernel can lead to system crashes and compromise network connectivity. It is crucial to update the Linux Kernel to version 5.16.10 or later 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

The DSA (Distributed Switch Architecture) subsystem in the Linux Kernel enables the use of distributed switches, allowing network traffic to be distributed across multiple physical devices. It provides a flexible and scalable solution for managing network connectivity in complex environments.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and Vulert will analyze it in real-time to identify any open-source vulnerabilities, including this one.

The vulnerability can lead to a system crash (panic) when the DSA master device is unbound during system shutdown. This can disrupt network connectivity and compromise the stability of the system.

There is no information available regarding exploitation of this vulnerability in the wild. However, it is always recommended to apply security updates promptly to mitigate potential risks.

The only known mitigation for this vulnerability is to update the Linux Kernel to version 5.16.10 or later. It is important to keep the system up to date with the latest security patches to minimize the risk of exploitation.

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