CVE-2026-90127

virtio: rtc: time out alarm requests

Published Sep 17, 2026 CVSS n/a EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The vulnerability occurs when virtio‑RTC alarm requests wait indefinitely for a buffer return, because the driver holds ops_lock while blocking. The missing timeout causes the removal routine to deadlock on ops_lock, which can result in a stuck kernel thread. This behavior is inferred to produce a denial‑of‑service condition, as the hanging thread can stall system operations.

Affected Systems

This flaw affects the virtio‑RTC driver implementation in the Linux kernel. Any distribution or system running a Linux kernel that includes the unpatched virtio‑RTC code is at risk; no specific version range is listed, so all kernels prior to the patch that still use this module are potentially vulnerable.

Risk and Exploitability

The EPSS score is under 1 % and the vulnerability is not listed in CISA KEV, indicating a low current exploitation probability. The likely attack vector requires privileged or virtual‑environment control to force a virtio device to be removed or break. The post‑patch fix introduces a 60‑second timeout to prevent indefinite blocking, reducing the impact considerably if the patch is applied.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the Linux kernel to a release that includes the 60‑second timeout for virtio‑RTC alarm requests.
  • If a kernel upgrade cannot be performed immediately, disable or remove virtio‑RTC devices from the virtual environment to eliminate the hang condition.
  • Apply any available backport or patch that implements the timeout logic in the virtio‑RTC driver.

Generated by OpenCVE AI on September 20, 2026 at 03:12 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-9019-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9020-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9160-1 Linux kernel (Azure) vulnerabilities
History
Type Values Removed Values Added
Weaknesses CWE-666
Type Values Removed Values Added
Description 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.
Title virtio: rtc: time out alarm requests
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses
  • CWE-666

    Operation on Resource in Wrong Phase of Lifetime

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 19, 2026, 8:58 AM
Reserved
Sep 11, 2026, 7:38 PM
Status
Received
Published
Sep 17, 2026, 5:17 PM
Modified
Oct 19, 2026, 9:19 AM