Vulnerability in Kernel: mmc: core: use sysfs_emit() instead of sprintf()

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1001295: mmc: core: use sysfs_emit() instead of sprintf(). Affects Kernel versions < c4ab65738ab3e21fe519ee46b2051222bc8e32ef. 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 Kernel is a crucial component of the Linux operating system that acts as a bridge between the hardware and software layers. It provides essential functionalities and services to enable the proper functioning of the system. The mmc (MultiMediaCard) subsystem within the Kernel handles communication with SD and MMC memory cards. It allows devices to read and write data to these storage media.

The vulnerability in question arises from the use of sprintf() instead of sysfs_emit() in the mmc core. This vulnerability can potentially lead to security issues, although the exact impact and likelihood of exploitation have not been confirmed.

Vulnerability Detail

The vulnerability lies in the mmc core of the Kernel, where sprintf() is used instead of sysfs_emit(). This can result in security vulnerabilities, although the specific details and attack vectors are yet to be determined. The vulnerability has been assigned the ID GSD-2022-1001295 and is fixed in Linux Kernel version v5.17.2 by commit c4ab65738ab3e21fe519ee46b2051222bc8e32ef.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.17.2 or later. This can be done by pulling the latest changes from the official Linux Kernel repository and rebuilding the Kernel. Alternatively, users can wait for their Linux distribution to provide an updated package that includes the fix.

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 commit c4ab65738ab3e21fe519ee46b2051222bc8e32ef in the Linux Kernel repository. Users can then apply the patch using standard patching techniques.

Conclusion

In conclusion, the vulnerability in the Kernel's mmc core, caused by the use of sprintf() instead of sysfs_emit(), can potentially lead to security issues. It is recommended to update the Kernel to version v5.17.2 or later to fix this vulnerability. Alternatively, users can apply the provided patch manually. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The exact impact of this vulnerability is yet to be determined. However, it has the potential to lead to security issues.

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, and Vulert will analyze it for any open-source vulnerabilities, including this one.

At the time of writing, there is no known exploit for this vulnerability. However, it is still important to apply the fix or workaround to ensure the security of your system.

While updating the Kernel is the recommended solution, you can apply the provided patch manually to mitigate the risk temporarily. However, it is advisable to update to the latest Kernel version as soon as possible.

You can find more information about this vulnerability in the GSD-2022-1001295 entry of the GSD database maintained by the Cloud Security Alliance. The link to the specific entry is available in the vulnerability details section.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.17.2 or later. This can be done by pulling the latest changes from the official Linux Kernel repository and rebuilding the Kernel. Alternatively, users can wait for their Linux distribution to provide an updated package that includes the fix.

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.