{"id":"CVE-2026-90127","title":"In the Linux kernel, the following vulnerability has been resolved:\n\nvirtio: rtc: time out alarm requests\n\nRTC class operations run with rtc_device.ops_lock held","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\nvirtio: rtc: time out alarm requests\n\nRTC class operations run with rtc_device.ops_lock held. The virtio RTC\nalarm requests currently wait without a timeout for the dev…","severity":"none","vendor":"Linux","product":"Linux","affected":["Linux >= 9d4f22fd563e0cd02e8448e84d057e7c0132a586 < 28701b74c22d2a43ddf7aebb6378e60c18323865","Linux >= 9d4f22fd563e0cd02e8448e84d057e7c0132a586 < afbf69d1d691c06d093d7c3f17168ecb608c4977","Linux >= 9d4f22fd563e0cd02e8448e84d057e7c0132a586 < 68e00d9212929805b40dcb9166755610f4f4acee","Linux 6.16"],"published":"2026-09-17","updated":"2026-09-17","sourceUpdated":"2026-09-17T17:17:05.080","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-90127","references":[{"url":"https://git.kernel.org/stable/c/28701b74c22d2a43ddf7aebb6378e60c18323865","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/68e00d9212929805b40dcb9166755610f4f4acee","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/afbf69d1d691c06d093d7c3f17168ecb608c4977","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"}],"tags":["nvd","cve.org"],"ingestedAt":"2026-09-17T16:21:47.882Z","epss":0.00198,"epssPercentile":0.09849,"slug":"CVE-2026-90127","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvirtio: rtc: time out alarm requests\n\nRTC class operations run with rtc_device.ops_lock held. The virtio RTC\nalarm requests currently wait without a timeout for the device to return\ntheir requestq buffers.\n\nOn surprise removal, virtio-pci marks the virtqueues broken before\nunregistering the virtio device. If an alarm request is waiting when the\ndevice stops responding, viortc_remove() blocks in viortc_class_stop()\nwhile trying to acquire ops_lock. The request cannot complete and device\nremoval hangs until the waiting task is signalled.\n\nUse the same 60-second timeout as clock read requests for alarm reads,\nalarm programming, and alarm interrupt enable requests. The existing\nmessage reference counting keeps a timed-out request alive until a late\nresponse or device teardown.\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}