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-1001160: memstick/mspro_block: fix handling of read-only devices. Affects Kernel versions < 6a0725b9d78ff6efdc95a37e4f05072e79c63918. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

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 that affects its 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 code, which fails to properly handle read-only devices. As a result, an attacker could bypass the intended read-only protection and modify data on these devices. This vulnerability poses a significant risk to the integrity and confidentiality of data stored on read-only memory stick and memory stick pro 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 apply the recommended fix by updating the Linux Kernel to the specified version.

Conclusion

The memstick/mspro_block package in the Linux Kernel is vulnerable to a flaw that allows unauthorized access and data manipulation on read-only memory stick and memory stick pro devices. To mitigate this risk, it is crucial to update the Linux Kernel to version v5.17.2 or later, which includes the necessary fix. There are no known workarounds for this vulnerability. For additional support, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability allows an attacker to bypass read-only protection on memory stick and memory stick pro devices, potentially leading to unauthorized access or data manipulation.

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 for any open-source vulnerabilities, including this one.

At the time of this report, there are no known exploits for this vulnerability. However, it is crucial to apply the recommended fix to mitigate the risk.

No, this vulnerability requires physical access to the read-only memory stick or memory stick pro device. However, it is still important to address the issue to prevent potential unauthorized access or data manipulation.

For further support on vulnerability remediation, you can reach out to info@devnack.com. They can provide guidance and assistance in addressing this vulnerability.

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