Buffer Overflow Vulnerability in wl1251_cmd_scan

Kernel Updated 02 Oct 2025

Summary

03/08/2021
N/A
No i
Unrated
Not published

GSD-2021-1001296: wl1251: Fix possible buffer overflow in wl1251_cmd_scan. Affects Kernel versions < c5e4a10d7bd5d4f419d8b9705dff60cf69b302a1. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The wl1251 package is part of the Linux Kernel ecosystem and is responsible for managing wireless communication using the wl1251 chipset. It provides functionality for scanning and connecting to wireless networks. The vulnerability in question is related to a possible buffer overflow in the wl1251_cmd_scan function.

Vulnerability Detail

The vulnerability arises from a potential buffer overflow in the wl1251_cmd_scan function. If exploited, an attacker could overwrite adjacent memory locations, leading to arbitrary code execution or a system crash. The impact and attack plausibility of this vulnerability have not been proven yet. The vulnerability has been fixed in Linux Kernel version v5.10.51 by commit c5e4a10d7bd5d4f419d8b9705dff60cf69b302a1.

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 specific workaround mentioned for this vulnerability.

Conclusion

The buffer overflow vulnerability in wl1251_cmd_scan can be mitigated by updating the Linux Kernel to version v5.10.51 or later. It is important to stay updated with security patches to ensure the integrity and security of the system. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The impact of this vulnerability could potentially lead to arbitrary code execution or a system crash.

There is no evidence of this vulnerability being exploited in the wild at the moment.

Yes, the vulnerability has been fixed in Linux Kernel version v5.10.51 by commit c5e4a10d7bd5d4f419d8b9705dff60cf69b302a1.

Updating the kernel is the recommended approach to mitigate the risk. However, if updating is not feasible, other security measures like network segmentation and access controls can help reduce the attack surface.

You can find more information about this vulnerability in the Open Source Vulnerability Database (OSVDB) under the ID GSD-2021-1001296.

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