Skip to main content
VulnerabilityPublished Updated

CVE-2024-56739: Linux kernel · rtc: check if __rtc_read_time was successful in rtc_timer_do_work()

Source GCVE Database

0
Compare

Not known to be exploited · CVSS 5.5 Medium.

Data as of 30 Oct 2026, 00:54 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Dec 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

AI-suggested

The vulnerability has been resolved in the Linux kernel. Although no explicit patch links are provided here, the description states it has been fixed. Users should update their Linux kernel to the latest version containing this fix to prevent kernel softlockup issues related to RTC timer handling.

Description

CVE-2024-56739 is a vulnerability in the Linux kernel's RTC (Real-Time Clock) subsystem where a failure to check the success of the __rtc_read_time call in rtc_timer_do_work() can lead to uninitialized or invalid time data. This may cause the kernel to compute an excessively large time value, potentially triggering continuous expiration of periodic timers and resulting in a kernel softlockup.

References

Community reviews

Loading reviews…