Strix
75.5K

CVE-2026-74614

HIGHCVSS 8.4/10EPSS 0.14%

Last modified

CVE-2026-74614 is a high-severity vulnerability rated 8.4/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: vsock/virtio: read virtqueues under worker locks Commit bd50c5dc182b ("vsock/virtio: add support for device suspend/resume") made the *_run flags transition from false to true when restore installs replacement virtqueues. The RX, TX and event workers read their virtqueue before locking and checking the corresponding flag, so a worker delayed across freeze and restore can observe the replacement queue's running state while retaining a pointer to the deleted queue. Read each virtqueue under its mutex after checking the run flag, keeping the pointer and state in the same queue generation.. EPSS estimates a 0.14% chance of exploitation in the next 30 days.

Description

In the Linux kernel, the following vulnerability has been resolved: vsock/virtio: read virtqueues under worker locks Commit bd50c5dc182b ("vsock/virtio: add support for device suspend/resume") made the *_run flags transition from false to true when restore installs replacement virtqueues. The RX, TX and event workers read their virtqueue before locking and checking the corresponding flag, so a worker delayed across freeze and restore can observe the replacement queue's running state while retaining a pointer to the deleted queue. Read each virtqueue under its mutex after checking the run flag, keeping the pointer and state in the same queue generation.

Metrics

CVSS 3.1
8.4/10

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS Probability
0.14%

3.1th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 762c251c7f5c4ee5bef71460c6e822ed293fd69f, < 941329ce14c5f481223a10d1d4c8b57ea7f3048a; >= bd50c5dc182b0a52599f87b429f9a5a9cbfc9b1c, < 29dd10583bf9d2744cd84b862e4257c0a5699570; >= bd50c5dc182b0a52599f87b429f9a5a9cbfc9b1c, < a1fb0c5b8a7c2753758aeced40971f99449dde0c; >= bd50c5dc182b0a52599f87b429f9a5a9cbfc9b1c, < eae099c764c7ebdb842eb1f638913e310bdd6513; >= bd50c5dc182b0a52599f87b429f9a5a9cbfc9b1c, < bd43a7ec668be428265b3209eb43647aedcf720a; >= bd50c5dc182b0a52599f87b429f9a5a9cbfc9b1c, < 1cecb4202afdbeddcf29d59baf596ac6ab753f7f; >= bd50c5dc182b0a52599f87b429f9a5a9cbfc9b1c, < ebac8f6b1ef0e9278afe204b8692a7479988dace; >= 5.15.138, < 5.15.216
LinuxLinux5.19

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-74614?
In the Linux kernel, the following vulnerability has been resolved: vsock/virtio: read virtqueues under worker locks Commit bd50c5dc182b ("vsock/virtio: add support for device suspend/resume") made the *_run flags transition from false to true when restore installs replacement virtqueues. The RX, TX and event workers read their virtqueue before locking and checking the corresponding flag, so a worker delayed across freeze and restore can observe the replacement queue's running state while retaining a pointer to the deleted queue. Read each virtqueue under its mutex after checking the run flag, keeping the pointer and state in the same queue generation.
How severe is CVE-2026-74614?
CVE-2026-74614 has a CVSS score of 8.4/10 (HIGH severity). The EPSS model estimates a 0.14% probability of exploitation in the next 30 days.
How do I fix CVE-2026-74614?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-74614?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST