CVE-2026-99684
What it is
In the Linux kernel, the following vulnerability has been resolved: hwrng: virtio - prevent use-after-free after a failed restore remove_common() frees the driver data during freeze, but does not clear vdev->priv, which points to freed memory. If probe_common() then fails during restore, a later remove or freeze can dereference the dangling pointer. Clear vdev->priv on the probe_common() error cleanup path and before freeing the driver data in remove_common(). Also reset the device and return early from remove_common() if vdev->priv is already NULL for a safe teardown after a failed restore.
At a glance
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: not scored yet.
- Severity: not scored yet.
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Record status
- Received
Affected
- Linux < ec81f97c6b13b839e5800cdade1e5b187b9b2738
- Linux < 42f2f4ee9d6e75b8b55b9108f6f5cf254425db64
- Linux < b18bda055c0d3e44fdf419e2739d92ea92a6f1d2
- Linux < 0f7bf47f5a0cc26320aa4b14f4504d03a07f4b74
- Linux 3.16
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-99684.md and follow it. Check whether this project is affected by CVE-2026-99684. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.