CVE-2026-74311
Last modified
CVE-2026-74311 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: virtio: rtc: tear down old virtqueues before restore virtio_device_restore() resets the device and restores the negotiated features before calling ->restore(). viortc_freeze() intentionally leaves the existing virtqueues in place so the alarm queue can still wake the system, but viortc_restore() immediately calls viortc_init_vqs() without first deleting those old queues. If virtqueue reinitialization fails on virtio-pci, the transport error path can run vp_del_vqs() against a newly allocated vp_dev->vqs array while vdev->vqs still contains the old virtqueues. EPSS estimates a 0.17% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: virtio: rtc: tear down old virtqueues before restore virtio_device_restore() resets the device and restores the negotiated features before calling ->restore(). viortc_freeze() intentionally leaves the existing virtqueues in place so the alarm queue can still wake the system, but viortc_restore() immediately calls viortc_init_vqs() without first deleting those old queues. If virtqueue reinitialization fails on virtio-pci, the transport error path can run vp_del_vqs() against a newly allocated vp_dev->vqs array while vdev->vqs still contains the old virtqueues. vp_del_vqs() then looks up queue state through the new array and can dereference a NULL info pointer in vp_del_vq(), crashing the guest kernel during restore. This can also happen during a non-faulty reinitialization, when one of the vp_find_vqs_msix() attempts is unsuccessful before a later attempt would succeed. Delete the stale virtqueues before rebuilding them. If restore fails before virtio_device_ready(), reuse the remove path to stop the device. Once the device is ready, return errors directly instead of deleting the virtqueues again.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 0623c759276885c3ae88197ba6fb5c9c6ba8612f, < 79366023aa891ca31376021a7bccff6384ca1ff1; >= 0623c759276885c3ae88197ba6fb5c9c6ba8612f, < aebebd1e9d70b650fc9e877082e0134edcf511da; >= 0623c759276885c3ae88197ba6fb5c9c6ba8612f, < 548d2208455f14e6121404c6e30e997bfe0cd264 |
| Linux | Linux | 6.16 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-74311?
How severe is CVE-2026-74311?
How do I fix CVE-2026-74311?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-74306In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-74307In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74308In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74309In the Linux kernel, the following vulnerability has been re…10
- CVE-2026-7431An incorrect permission assignment for critical resource of …4.4
- CVE-2026-74310In the Linux kernel, the following vulnerability has been re…9.3
- CVE-2026-74312In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-74313In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-74314In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-74315In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-74316In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-74317In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2026-74311?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
