CVE-2024-56739: rtc: check if __rtc_read_time was successful in rtc_timer_do_work()
First published: Sun Dec 29 2024(Updated: )
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.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | >=2.6.38<4.19.325 | |
| Linux Kernel | >=4.20<5.4.287 | |
| Linux Kernel | >=5.5<5.10.231 | |
| Linux Kernel | >=5.11<5.15.174 | |
| Linux Kernel | >=5.16<6.1.120 | |
| Linux Kernel | >=6.2<6.6.64 | |
| Linux Kernel | >=6.7<6.11.11 | |
| Linux Kernel | >=6.12<6.12.2 | |
| debian/linux | <=5.10.223-1 | 5.10.234-1 6.1.129-1 6.1.128-1 6.12.20-1 6.12.21-1 |
| debian/linux-6.1 | 6.1.129-1~deb11u1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/39ad0a1ae17b54509cd9e93dcd8cec16e7c12d3f
- https://git.kernel.org/stable/c/44b3257ff705d63d5f00ef8ed314a0eeb7ec37f2
- https://git.kernel.org/stable/c/0d68e8514d9040108ff7d1b37ca71096674b6efe
- https://git.kernel.org/stable/c/246f621d363988e7040f4546d20203dc713fa3e1
- https://git.kernel.org/stable/c/fde56535505dde3336df438e949ef4742b6d6d6e
- https://git.kernel.org/stable/c/dd4b1cbcc916fad5d10c2662b62def9f05e453d4
- https://git.kernel.org/stable/c/a1f0b4af90cc18b10261ecde56c6a56b22c75bd1
- https://git.kernel.org/stable/c/e77bce0a8c3989b4173c36f4195122bca8f4a3e1
- https://git.kernel.org/stable/c/e8ba8a2bc4f60a1065f23d6a0e7cbea945a0f40d
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-56739
- https://nvd.nist.gov/vuln/detail/CVE-2024-56739
- https://launchpad.net/bugs/cve/CVE-2024-56739
- https://security-tracker.debian.org/tracker/CVE-2024-56739
- https://ubuntu.com/security/CVE-2024-56739
- https://git.kernel.org/linus/e8ba8a2bc4f60a1065f23d6a0e7cbea945a0f40d
Frequently Asked Questions
What is the severity of CVE-2024-56739?
CVE-2024-56739 is considered a medium severity vulnerability due to potential exposure to uninitialized data.
How do I fix CVE-2024-56739?
To mitigate CVE-2024-56739, upgrade the Linux kernel to a version that addresses this vulnerability.
Which versions of the Linux kernel are affected by CVE-2024-56739?
CVE-2024-56739 affects Linux kernel versions from 2.6.38 up to 6.12.2.
What is the impacts of CVE-2024-56739?
The impact of CVE-2024-56739 may include the use of uninitialized data leading to unreliable or improper date and time readings.
Is there a workaround for CVE-2024-56739?
Currently, there are no recommended workarounds for CVE-2024-56739, so applying the patch is essential.
- agent/title
- agent/first-publish-date
- agent/type
- agent/author
- agent/severity
- agent/remedy
- agent/weakness
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/references
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/nvd-cve
- collector/usn-cve
- source/Ubuntu
- collector/launchpad-cve
- source/Launchpad
- agent/source
- agent/softwarecombine
- agent/tags
- agent/description
- agent/event
- collector/security-tracker-debian
- source/Debian
- vendor/linux
- canonical/linux kernel
- version/linux kernel/2.6.38
- version/linux kernel/4.20
- version/linux kernel/5.5
- version/linux kernel/5.11
- version/linux kernel/5.16
- version/linux kernel/6.2
- version/linux kernel/6.7
- version/linux kernel/6.12
- package-manager/debian