Linux Kernel up to 5.15.32/5.16.18/5.17.1 RTC_FEATURE_ALARM null pointer dereference

Summaryinfo

A vulnerability labeled as problematic has been found in Linux Kernel up to 5.15.32/5.16.18/5.17.1. Affected by this vulnerability is the function RTC_FEATURE_ALARM. The manipulation results in null pointer dereference. This vulnerability is cataloged as CVE-2022-49273. There is no exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability classified as problematic has been found in Linux Kernel up to 5.15.32/5.16.18/5.17.1. Affected is the function RTC_FEATURE_ALARM. The manipulation with an unknown input leads to a null pointer dereference vulnerability. CWE is classifying the issue as CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. This is going to have an impact on availability. CVE summarizes:

In the Linux kernel, the following vulnerability has been resolved: rtc: pl031: fix rtc features null pointer dereference When there is no interrupt line, rtc alarm feature is disabled. The clearing of the alarm feature bit was being done prior to allocations of ldata->rtc device, resulting in a null pointer dereference. Clear RTC_FEATURE_ALARM after the rtc device is allocated.

The advisory is available at git.kernel.org. This vulnerability is traded as CVE-2022-49273 since 02/26/2025. Technical details are known, but there is no available exploit.

The vulnerability scanner Nessus provides a plugin with the ID 225793 (Linux Distros Unpatched Vulnerability : CVE-2022-49273), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 5.15.33, 5.16.19 or 5.17.2 eliminates this vulnerability. Applying the patch cd2722e411e8ab7e5ae41102f6925fa13dffdac5/d274ce4a3dfd0b9a292667535578359b865765cb/1b915703964f7e636961df04c540261dc55c6c70/ea6af39f3da50c86367a71eb3cc674ade3ed244c is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at Tenable (225793). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 5.15.0
• 5.15.1
• 5.15.2
• 5.15.3
• 5.15.4
• 5.15.5
• 5.15.6
• 5.15.7
• 5.15.8
• 5.15.9
• 5.15.10
• 5.15.11
• 5.15.12
• 5.15.13
• 5.15.14
• 5.15.15
• 5.15.16
• 5.15.17
• 5.15.18
• 5.15.19
• 5.15.20
• 5.15.21
• 5.15.22
• 5.15.23
• 5.15.24
• 5.15.25
• 5.15.26
• 5.15.27
• 5.15.28
• 5.15.29
• 5.15.30
• 5.15.31
• 5.15.32
• 5.16.0
• 5.16.1
• 5.16.2
• 5.16.3
• 5.16.4
• 5.16.5
• 5.16.6
• 5.16.7
• 5.16.8
• 5.16.9
• 5.16.10
• 5.16.11
• 5.16.12
• 5.16.13
• 5.16.14
• 5.16.15
• 5.16.16
• 5.16.17
• 5.16.18
• 5.17.0
• 5.17.1

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion