Data corruption or loss via unchecked virtio length
Published Aug 7, 2021 · Updated Aug 4, 2024
Buffer length validation failure in the Linux kernel before 5.13.4 allows an untrusted virtio device to cause data corruption or loss. The get_inbuf and control_work_handler paths assign the device-reported virtqueue length to buf->len without limiting it to buf->size, allowing later processing to trust a length larger than the buffer. Reachability requires an untrusted device, and the vendor states that no existing use case makes the robustness defect a security vulnerability.
Summary
What happened
Buffer length validation failure in the Linux kernel before 5.13.4 allows an untrusted virtio device to cause data corruption or loss. The get_inbuf and control_work_handler paths assign the device-reported virtqueue length to buf->len without limiting it to buf->size, allowing later processing to trust a length larger than the buffer. Reachability requires an untrusted device, and the vendor states that no existing use case makes the robustness defect a security vulnerability.
The record
- CVE
- CVE-2021-38160
- Published
- Aug 7, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 7, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo