In the Linux kernel, the following vulnerability has been resolved: vsock/virtio: read virtqueues under worker locks Commit bd50c5dc182b… (CVE-2026-74614)
A vulnerability in the Linux kernel's vsock/virtio component was resolved involving improper handling of virtqueues under worker locks. The issue arose because worker threads could read virtqueues without proper locking after device suspend/resume operations, potentially leading to use of stale pointers. The fix ensures virtqueues are read under mutex locks after checking run flags, preventing access to deleted queues.
AI Analysis
Technical Summary
The vulnerability (CVE-2026-74614) in the Linux kernel's vsock/virtio subsystem was introduced by commit bd50c5dc182b, which changed the handling of *_run flags during device suspend/resume. Worker threads (RX, TX, and event workers) read virtqueues before acquiring locks and checking run flags, which could cause them to access replacement virtqueues' running state while still holding pointers to deleted queues. The patch modifies the code to read each virtqueue under its mutex after verifying the run flag, ensuring pointer and state consistency within the same queue generation.
Potential Impact
The vulnerability could lead to worker threads accessing stale or deleted virtqueue pointers, potentially causing undefined behavior or kernel instability. No information about exploitation in the wild or specific impacts such as privilege escalation or denial of service is provided.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this issue by adding proper locking when reading virtqueues. Users should apply the official kernel updates that include this patch. Patch status is not explicitly confirmed in the provided data; users should consult the vendor advisory or Linux kernel mailing lists for the exact fixed versions and update accordingly.
In the Linux kernel, the following vulnerability has been resolved: vsock/virtio: read virtqueues under worker locks Commit bd50c5dc182b… (CVE-2026-74614)
Description
A vulnerability in the Linux kernel's vsock/virtio component was resolved involving improper handling of virtqueues under worker locks. The issue arose because worker threads could read virtqueues without proper locking after device suspend/resume operations, potentially leading to use of stale pointers. The fix ensures virtqueues are read under mutex locks after checking run flags, preventing access to deleted queues.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability (CVE-2026-74614) in the Linux kernel's vsock/virtio subsystem was introduced by commit bd50c5dc182b, which changed the handling of *_run flags during device suspend/resume. Worker threads (RX, TX, and event workers) read virtqueues before acquiring locks and checking run flags, which could cause them to access replacement virtqueues' running state while still holding pointers to deleted queues. The patch modifies the code to read each virtqueue under its mutex after verifying the run flag, ensuring pointer and state consistency within the same queue generation.
Potential Impact
The vulnerability could lead to worker threads accessing stale or deleted virtqueue pointers, potentially causing undefined behavior or kernel instability. No information about exploitation in the wild or specific impacts such as privilege escalation or denial of service is provided.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this issue by adding proper locking when reading virtqueues. Users should apply the official kernel updates that include this patch. Patch status is not explicitly confirmed in the provided data; users should consult the vendor advisory or Linux kernel mailing lists for the exact fixed versions and update accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-m75m-8448-cc2j
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-74614"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a8a27f2acd9273b499bc80a
Added to database: 08/22/2026, 22:51:30 UTC
Last enriched: 08/22/2026, 23:52:58 UTC
Last updated: 08/23/2026, 00:32:12 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.