rtc: check if __rtc_read_time was successful in rtc_timer_do_work()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 6610e0893b8bc6f59b14fed7f089c5997f035f88 · < dd4b1cbcc916fad5d10c2662b62def9f05e453d4| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's RTC timer work may use uninitialized or invalid time data if an RTC read fails. If periodic timers are queued, this can cause them to expire continuously and may softlock the kernel. The input does not specify an attacker action, access requirements, or user interaction.
Operators running the Linux kernel should check their systems; affected versions are not specified.