Null Pointer Dereference in rtc: pl031

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1001612: rtc: pl031: fix rtc features null pointer dereference. Affects Kernel versions >= d9b0dd54a1943f47a381a474f8ea2c94466110c0, < d274ce4a3dfd0b9a292667535578359b865765cb. 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 rtc: pl031 is a driver in the Linux Kernel responsible for handling the Real-Time Clock (RTC) functionality on ARM-based systems. The RTC provides the system with accurate timekeeping capabilities, which are crucial for various system operations and applications. However, a vulnerability has been discovered in the rtc: pl031 driver that can lead to a null pointer dereference.

Vulnerability Detail

The null pointer dereference vulnerability in the rtc: pl031 driver occurs when certain features of the RTC are accessed without proper validation of a pointer. This can result in a crash or system instability, potentially leading to a denial of service (DoS) condition. An attacker may be able to exploit this vulnerability to disrupt system operations or cause a system crash. The vulnerability was introduced in Linux Kernel version v5.12 and has been fixed in version v5.16.19.

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.16.19 or later. This can be done by obtaining the latest kernel source code from the official Linux Kernel repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/) and compiling it for the target system. Alternatively, users can wait for their Linux distribution to provide an updated kernel 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

There is no known workaround for this vulnerability. It is recommended to apply the fix mentioned in the 'how_to_fix' section.

Conclusion

The null pointer dereference vulnerability in the rtc: pl031 driver can lead to system crashes and instability. It is crucial to update the Linux Kernel to version v5.16.19 or later to mitigate this vulnerability. For further support and assistance with vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability can lead to a null pointer dereference, resulting in a crash or system instability. This can potentially be exploited by an attacker to cause a denial of service (DoS) condition.

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 is no known exploit for this vulnerability. However, it is still important to apply the fix to prevent any potential exploitation.

The recommended approach is to update the Linux Kernel to the fixed version. However, if updating is not immediately feasible, it is crucial to ensure other security measures are in place, such as network segmentation, access controls, and monitoring for any suspicious activity.

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.16.19 or later. This can be done by obtaining the latest kernel source code from the official Linux Kernel repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/) and compiling it for the target system. Alternatively, users can wait for their Linux distribution to provide an updated kernel 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.