{"api_version":"1","generated_at":"2026-10-03T07:07:21+00:00","cve":"CVE-2026-90127","urls":{"html":"https://cve.report/CVE-2026-90127","api":"https://cve.report/api/cve/CVE-2026-90127.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-90127","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-90127"},"summary":{"title":"virtio: rtc: time out alarm requests","description":"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 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.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-17 17:17:05","updated_at":"2026-09-17 17:17:05"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/68e00d9212929805b40dcb9166755610f4f4acee","name":"https://git.kernel.org/stable/c/68e00d9212929805b40dcb9166755610f4f4acee","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/afbf69d1d691c06d093d7c3f17168ecb608c4977","name":"https://git.kernel.org/stable/c/afbf69d1d691c06d093d7c3f17168ecb608c4977","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/28701b74c22d2a43ddf7aebb6378e60c18323865","name":"https://git.kernel.org/stable/c/28701b74c22d2a43ddf7aebb6378e60c18323865","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-90127","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90127","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 9d4f22fd563e0cd02e8448e84d057e7c0132a586 28701b74c22d2a43ddf7aebb6378e60c18323865 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 9d4f22fd563e0cd02e8448e84d057e7c0132a586 afbf69d1d691c06d093d7c3f17168ecb608c4977 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 9d4f22fd563e0cd02e8448e84d057e7c0132a586 68e00d9212929805b40dcb9166755610f4f4acee git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.16","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.16 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.52 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.6 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/virtio/virtio_rtc_driver.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"28701b74c22d2a43ddf7aebb6378e60c18323865","status":"affected","version":"9d4f22fd563e0cd02e8448e84d057e7c0132a586","versionType":"git"},{"lessThan":"afbf69d1d691c06d093d7c3f17168ecb608c4977","status":"affected","version":"9d4f22fd563e0cd02e8448e84d057e7c0132a586","versionType":"git"},{"lessThan":"68e00d9212929805b40dcb9166755610f4f4acee","status":"affected","version":"9d4f22fd563e0cd02e8448e84d057e7c0132a586","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/virtio/virtio_rtc_driver.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.16"},{"lessThan":"6.16","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.52","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.6","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.52","versionStartIncluding":"6.16","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.6","versionStartIncluding":"6.16","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc1","versionStartIncluding":"6.16","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"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 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."}],"providerMetadata":{"dateUpdated":"2026-09-17T16:06:29.219Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/28701b74c22d2a43ddf7aebb6378e60c18323865"},{"url":"https://git.kernel.org/stable/c/afbf69d1d691c06d093d7c3f17168ecb608c4977"},{"url":"https://git.kernel.org/stable/c/68e00d9212929805b40dcb9166755610f4f4acee"}],"title":"virtio: rtc: time out alarm requests","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-90127","datePublished":"2026-09-17T16:06:29.219Z","dateReserved":"2026-09-11T19:38:34.788Z","dateUpdated":"2026-09-17T16:06:29.219Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-17 17:17:05","lastModifiedDate":"2026-09-17 17:17:05","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"90127","Ordinal":"1","Title":"virtio: rtc: time out alarm requests","CVE":"CVE-2026-90127","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"90127","Ordinal":"1","NoteData":"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 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.","Type":"Description","Title":"virtio: rtc: time out alarm requests"}]}}}