Vulnerability in memstick/mspro_block package: Fix handling of read-only devices

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1001483: memstick/mspro_block: fix handling of read-only devices. Affects Kernel versions < 057b53c4f87690d626203acef8b63d52a9bf2f43. 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 memstick/mspro_block package is a component of the Linux Kernel, which is responsible for handling memory stick and memory stick pro devices. These devices are commonly used for data storage and transfer. The package provides the necessary functionality to interact with these devices, including reading and writing data. However, a vulnerability has been discovered in the package's handling of read-only devices.

Vulnerability Detail

The vulnerability in the memstick/mspro_block package allows an attacker to exploit read-only devices, potentially leading to unauthorized access or data manipulation. The issue originates from a flaw in the package's implementation, which fails to properly handle read-only devices. This could allow an attacker to bypass intended restrictions and perform malicious actions on the device. The impact of this vulnerability can vary depending on the specific use case, but it has the potential to compromise the integrity and confidentiality of data stored on read-only devices.

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 essential to update the Linux Kernel to the recommended version to mitigate the risk.

Conclusion

In conclusion, the memstick/mspro_block package in the Linux Kernel is vulnerable to an issue that allows attackers to exploit read-only devices. To mitigate this risk, it is crucial to update the Linux Kernel to version v5.16.19 or later. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The memstick/mspro_block package is a component of the Linux Kernel that handles memory stick and memory stick pro devices.

The vulnerability allows an attacker to exploit read-only devices, potentially leading to unauthorized access or data manipulation.

To fix this vulnerability, update the Linux Kernel to version v5.16.19 or later.

No, there is no known workaround. Updating the Linux Kernel is the recommended solution.

For more details about this vulnerability, refer to the provided references link.

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