Root escalation via TTY-owner confusion
Published Aug 11, 2026 · Updated Aug 11, 2026
Improper access control in kbd openvt allows local users to gain root access through a privileged keyboard-request configuration. authenticate_user() follows /proc process-file-descriptor links and mistakes the TTY device owner's UID for the process owner's UID. Exploitation requires non-default privileged kbrequest/init use of openvt -u, an attached unprivileged process, logout, and the resulting TTY ownership transition.
Summary
What happened
Improper access control in kbd openvt allows local users to gain root access through a privileged keyboard-request configuration. authenticate_user() follows /proc process-file-descriptor links and mistakes the TTY device owner's UID for the process owner's UID. Exploitation requires non-default privileged kbrequest/init use of openvt -u, an attached unprivileged process, logout, and the resulting TTY ownership transition.
The record
- CVE
- CVE-2026-72693
- Published
- Aug 11, 2026
- Updated
- Aug 11, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Enterprise Linux 10
- Classifications
- CWE-284, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 11, 2026CVE publishedPublication date reported by the CVE source.
- Aug 11, 2026Record 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
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
- Red Hat Bugzilla reproduction procedureproof of concept · demonstrated
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