Guest-memory read and write via unchecked grant revocation
Published Mar 10, 2022 · Updated Aug 3, 2024
Race condition in Linux xenbus PV frontends allows attackers controlling a PV backend to read or write guest memory through retained grant access. The xenbus driver fails to check whether revoking a shared ring-buffer grant succeeded, allowing the backend to retain access to the page. Exposure requires a Linux guest using PV devices with a potentially malicious backend; retained access crosses the guest boundary.
Summary
What happened
Race condition in Linux xenbus PV frontends allows attackers controlling a PV backend to read or write guest memory through retained grant access. The xenbus driver fails to check whether revoking a shared ring-buffer grant succeeded, allowing the backend to retain access to the page. Exposure requires a Linux guest using PV devices with a potentially malicious backend; retained access crosses the guest boundary.
The record
- CVE
- CVE-2022-23040
- Published
- Mar 10, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-362
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 10, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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