virtio: rtc: time out alarm requests
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 28701b74c22d2a43ddf7aebb6378e60c18323865, Kernel 68e00d9212929805b40dcb9166755610f4f4acee and Kernel afbf69d1d691c06d093d7c3f17168ecb608c4977.
In the Linux kernel, the following vulnerability has been resolved: virtio: rtc: time out alarm requests RTC class operations run with rtc_device.ops_lock held. The virtio RTC alarm requests currently wait without a timeout for the device to return their requestq buffers. On surprise removal, virtio-pci marks the virtqueues broken before unregistering the virtio device. If an alarm request is waiting when the device stops responding, viortc_remove() blocks in viortc_class_stop() while trying to acquire ops_lock. The request cannot complete and device removal hangs until the waiting task is signalled. Use the same 60-second timeout as clock read requests for alarm reads, alarm programming, and alarm interrupt enable requests. The existing message reference counting keeps a timed-out request alive until a late response or device teardown.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.16, >=9d4f22fd563e0cd02e8448e84d057e7c0132a586 <28701b74c22d2a43ddf7aebb6378e60c18323865, >=9d4f22fd563e0cd02e8448e84d057e7c0132a586 <68e00d9212929805b40dcb9166755610f4f4acee, >=9d4f22fd563e0cd02e8448e84d057e7c0132a586 <afbf69d1d691c06d093d7c3f17168ecb608c4977 | 28701b74c22d2a43ddf7aebb6378e60c18323865, 68e00d9212929805b40dcb9166755610f4f4acee, afbf69d1d691c06d093d7c3f17168ecb608c4977 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket