CVE-2026-97992 Linux CVE debrief

Who should care

Defenders responsible for Linux kernel security, particularly those managing environments using vhost-vdpa and VDUSE, should assess exposure and prioritize patching. This includes operators, platform administrators, vulnerability management teams, and security teams who need to ensure the security and integrity of their Linux kernel environments.

Why it matters

This vulnerability allows for potential privilege escalation and denial of service in Linux kernel environments using vhost-vdpa and VDUSE. Defenders should prioritize patching and configuration updates to prevent potential exploitation.

• Potential for privilege escalation
• Possible denial of service (DoS) via crash or instability
• Need for verification of patch application and configuration updates
• Potential for data tampering or unauthorized access

Technical summary

The vulnerability exists in the Linux kernel's vhost-vdpa component, specifically in the `vhost_vdpa_config_cb` function. The function loads `v->config_ctx` and signals it without taking a reference or holding a lock, allowing a use-after-free condition when `VHOST_VDPA_SET_CONFIG_CALL` replaces the field and drops the last reference to the old context. This issue allows for potential privilege escalation and denial of service in Linux kernel environments using vhost-vdpa and VDUSE. The vulnerability was resolved by adding a spinlock covering every access to `config_ctx`, ensuring the callback either signals a context that is still alive or observes NULL, and the put happens only once no callback can reach the

Defensive priority

Defenders should prioritize verifying and applying patches for this vulnerability, particularly in environments using vhost-vdpa and VDUSE.

Recommended defensive actions

• Verify and apply patches for this vulnerability
• Review and update configurations for vhost-vdpa and VDUSE
• Monitor for potential exploitation attempts
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability was resolved by adding a spinlock covering every access to `config_ctx`, ensuring the callback either signals a context that is still alive or observes NULL, and the put happens only once no callback can reach the old value.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.