qede: Confirm skb is Allocated Before Using

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1001978: qede: confirm skb is allocated before using. Affects Kernel versions >= 8a8633978b842c88fbcfe00d4e5dde96048f630e, < 8928239e5e2e460d95b8a0b89f61671625e7ece0. 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 qede package is a network driver for the QLogic FastLinQ Ethernet adapters. It is a part of the Linux Kernel ecosystem. The qede driver provides support for various QLogic adapters, enabling network connectivity and communication. However, a vulnerability has been discovered in the qede driver that could potentially lead to security issues.

Vulnerability Detail

The vulnerability in the qede driver arises from the failure to confirm whether a socket buffer (skb) is allocated before using it. This can result in the use of an unallocated skb, leading to potential memory corruption or other security vulnerabilities. The vulnerability was introduced in version v4.18 of the Linux Kernel and has been fixed in version v5.10.111.

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 manually to their existing kernel version. The patch can be obtained from the Linux Kernel repository. However, it is strongly advised to update to the latest stable version of the Linux Kernel to benefit from the comprehensive fix and other security enhancements.

Conclusion

The qede driver in the Linux Kernel is vulnerable to a security issue that arises from the use of unallocated socket buffers. To mitigate this vulnerability, it is essential to update the Linux Kernel to version v5.10.111 or later. Applying the fix will ensure that the qede driver no longer utilizes unallocated skb, reducing the risk of memory corruption and other potential security vulnerabilities. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability in the qede driver can potentially lead to memory corruption or other security vulnerabilities. Exploiting this vulnerability may allow an attacker to execute arbitrary code or cause a denial-of-service (DoS) condition.

You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file to the playground, and it will analyze and alert you if the vulnerability is present.

No, at the time of this report, there is no specific CVE assigned to this vulnerability. However, it is recommended to update to the latest version of the Linux Kernel to ensure the fix is applied.

At the time of this report, there are no known exploits for this vulnerability. However, it is crucial to apply the fix promptly to mitigate any potential risks.

While updating the Linux Kernel to the latest version is the primary measure to address this vulnerability, it is also recommended to follow general security best practices. This includes regularly updating all software components, implementing strong access controls, and monitoring for any suspicious network activity.

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