virtio: rtc: time out alarm requests
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.18.52, 7.2.6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 9d4f22fd563e0cd02e8448e84d057e7c0132a586 · fixed in 28701b74c22d2a43ddf7aebb6378e60c18323865; From 9d4f22fd563e0cd02e8448e84d057e7c0132a586 · fixed in afbf69d1d691c06d093d7c3f17168ecb608c4977; From 9d4f22fd563e0cd02e8448e84d057e7c0132a586 · fixed in 68e00d9212929805b40dcb9166755610f4f4acee
- Linux Linux
6.16
- KernelLinux
From 6.16.0 · fixed in 6.18.52; From 6.19.0 · fixed in 7.2.6