Kernel memory access via lockdown debugger trigger
Published Jun 9, 2022 · Updated Sep 24, 2024
Kernel debugger lockdown bypass in Oracle Linux and Oracle VM allows local users with serial-port access to read or write kernel memory. KGDB and KDB remain usable during lockdown because the debugger trigger path fails to enforce the lockdown restriction, permitting writes such as zeroing a chosen kernel location. Exploitation requires high privileges and direct serial access, with confidentiality, integrity, and availability impact.
Summary
What happened
Kernel debugger lockdown bypass in Oracle Linux and Oracle VM allows local users with serial-port access to read or write kernel memory. KGDB and KDB remain usable during lockdown because the debugger trigger path fails to enforce the lockdown restriction, permitting writes such as zeroing a chosen kernel location. Exploitation requires high privileges and direct serial access, with confidentiality, integrity, and availability impact.
The record
- CVE
- CVE-2022-21499
- Published
- Jun 9, 2022
- Updated
- Sep 24, 2024
- Vendor
- Oracle
- Product
- Oracle VM
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jun 9, 2022CVE publishedPublication date reported by the CVE source.
- Sep 24, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Oracle VM: 3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
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