Vulnerability in Kernel package: rtc: mt6397

Kernel Updated 02 Oct 2025

Summary

28/06/2022
N/A
No i
Unrated
Not published

GSD-2022-1003971: rtc: mt6397: check return value after calling platform_get_resource(). Affects Kernel versions >= fc2979118f3f5193475cb53d5df7bdaa7e358a42, < 79fa3f5758d8712df0678df98161f948fc4370e5. 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 Kernel package is a crucial component of the Linux operating system, responsible for managing the system's core functionality. It provides essential services such as process management, memory management, and device drivers. The rtc: mt6397 module within the Kernel package is specifically responsible for handling real-time clock (RTC) functionality on devices utilizing the MediaTek MT6397 chipset. This vulnerability affects the rtc: mt6397 module and can potentially lead to security issues.

Vulnerability Detail

The vulnerability in the rtc: mt6397 module arises from a failure to check the return value after calling the platform_get_resource() function. This oversight can result in various security risks, although the exact impact and likelihood of exploitation have not been confirmed. The vulnerability was introduced in version v4.2 of the Linux Kernel and has been addressed in version v4.14.283 through commit 79fa3f5758d8712df0678df98161f948fc4370e5.

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, developers can manually check the return value after calling the platform_get_resource() function in the rtc: mt6397 module. By validating the return value and handling any potential errors appropriately, the vulnerability can be mitigated. Here is an example code snippet demonstrating the workaround:

// Check return value after calling platform_get_resource()
struct resource *res = platform_get_resource(...);
if (!res) {
    // Handle error condition
}

Conclusion

In conclusion, the rtc: mt6397 module in the Kernel package is vulnerable due to a lack of proper return value checking after calling the platform_get_resource() function. This vulnerability can potentially lead to security breaches, although the exact impact is yet to be confirmed. It is highly recommended to update the Kernel package to version v4.14.283 or later to address this vulnerability. Alternatively, developers can implement the provided workaround to mitigate the risk. For further assistance or support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The exact impact of this vulnerability is not yet confirmed. However, it has the potential to be exploited for security breaches, which could lead to unauthorized access, data manipulation, or denial of service.

To check if your system is affected, you can use the Vulert Playground at Vulert Scanner. Simply upload your package-lock.json file, and Vulert will analyze it to identify any open-source vulnerabilities, including this specific vulnerability in the Kernel package.

As of now, there is no known exploit for this vulnerability. However, it is crucial to apply the recommended fix or workaround to mitigate any potential risks.

The remote exploitability of this vulnerability is yet to be determined. However, it is always advisable to address vulnerabilities promptly to minimize the risk of remote exploitation.

The primary solution to fix this vulnerability is to update the Linux Kernel package to the recommended version. However, if updating is not feasible or practical, implementing the provided workaround can help mitigate the vulnerability to some extent.

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