Bug 2334829 (CVE-2024-56739) - CVE-2024-56739 kernel: rtc: check if __rtc_read_time was successful in rtc_timer_do_work()
Summary: CVE-2024-56739 kernel: rtc: check if __rtc_read_time was successful in rtc_ti...
Keywords:
Status: NEW
Alias: CVE-2024-56739
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-12-29 12:02 UTC by OSIDB Bzimport
Modified: 2025-04-06 19:23 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2024-12-29 12:02:44 UTC
In the Linux kernel, the following vulnerability has been resolved:

rtc: check if __rtc_read_time was successful in rtc_timer_do_work()

If the __rtc_read_time call fails,, the struct rtc_time tm; may contain
uninitialized data, or an illegal date/time read from the RTC hardware.

When calling rtc_tm_to_ktime later, the result may be a very large value
(possibly KTIME_MAX). If there are periodic timers in rtc->timerqueue,
they will continually expire, may causing kernel softlockup.

Comment 1 Avinash Hanwate 2024-12-30 03:42:16 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2024122925-CVE-2024-56739-0a67@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.