Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
A vulnerability in the openvt utility (part of the kbd package) allows a local unprivileged attacker to achieve passwordless root login due to incorrect process owner verification. This occurs when a specific non-default kbrequest/init configuration uses openvt -u combined with a timing condition where TTY ownership has reverted to root after logout while an unprivileged process still holds an open file descriptor to that TTY. This flaw can lead to privilege escalation but requires deliberate configuration and a narrow race condition, which are not present in standard Red Hat deployments. Red Hat rates the impact as moderate despite a high technical severity score. The issue is addressed by avoiding the use of openvt -u in privileged kbrequest/init setups or disabling the keyboard request binding until a fix is available.
AI Analysis
Technical Summary
CVE-2026-72693 is a local privilege escalation vulnerability in openvt (kbd package) where the ownership verification of the process is flawed. The authenticate_user() function relies on stat("/proc/<pid>/fd/0") which returns the owner of the TTY device node, not the actual process owner. If the TTY ownership returns to root after logout while an unprivileged process still holds fd 0, the check can incorrectly authenticate the unprivileged process as the privileged console owner. This leads to passwordless login as root when openvt -u is used in kbrequest/init. Exploitation requires a non-default kbrequest/init configuration invoking openvt -u and a specific timing race condition. Standard Red Hat product deployments do not have this configuration, limiting real-world impact. Red Hat recommends avoiding openvt -u in privileged contexts or disabling the keyboard request binding until a fix is available.
Potential Impact
The vulnerability allows a local unprivileged attacker to escalate privileges to root without a password under specific conditions involving a non-default kbrequest/init configuration and a timing race condition with TTY ownership. The impact is high in a technical sense (passwordless root login), but real-world exploitation is constrained by the need for deliberate configuration and timing, resulting in a moderate overall impact rating by Red Hat.
Mitigation Recommendations
Red Hat advises avoiding the use of openvt -u in privileged kbrequest/init deployments. Instead, configure kbrequest to initiate a standard authenticated login on the new virtual terminal or disable the keyboard request binding entirely until a fix is available. Changes to kbrequest configurations may require a system restart or service reload. No official patch is currently indicated; mitigation relies on configuration changes.
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
Description
A vulnerability in the openvt utility (part of the kbd package) allows a local unprivileged attacker to achieve passwordless root login due to incorrect process owner verification. This occurs when a specific non-default kbrequest/init configuration uses openvt -u combined with a timing condition where TTY ownership has reverted to root after logout while an unprivileged process still holds an open file descriptor to that TTY. This flaw can lead to privilege escalation but requires deliberate configuration and a narrow race condition, which are not present in standard Red Hat deployments. Red Hat rates the impact as moderate despite a high technical severity score. The issue is addressed by avoiding the use of openvt -u in privileged kbrequest/init setups or disabling the keyboard request binding until a fix is available.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-72693 is a local privilege escalation vulnerability in openvt (kbd package) where the ownership verification of the process is flawed. The authenticate_user() function relies on stat("/proc/<pid>/fd/0") which returns the owner of the TTY device node, not the actual process owner. If the TTY ownership returns to root after logout while an unprivileged process still holds fd 0, the check can incorrectly authenticate the unprivileged process as the privileged console owner. This leads to passwordless login as root when openvt -u is used in kbrequest/init. Exploitation requires a non-default kbrequest/init configuration invoking openvt -u and a specific timing race condition. Standard Red Hat product deployments do not have this configuration, limiting real-world impact. Red Hat recommends avoiding openvt -u in privileged contexts or disabling the keyboard request binding until a fix is available.
Potential Impact
The vulnerability allows a local unprivileged attacker to escalate privileges to root without a password under specific conditions involving a non-default kbrequest/init configuration and a timing race condition with TTY ownership. The impact is high in a technical sense (passwordless root login), but real-world exploitation is constrained by the need for deliberate configuration and timing, resulting in a moderate overall impact rating by Red Hat.
Mitigation Recommendations
Red Hat advises avoiding the use of openvt -u in privileged kbrequest/init deployments. Instead, configure kbrequest to initiate a standard authenticated login on the new virtual terminal or disable the keyboard request binding entirely until a fix is available. Changes to kbrequest configurations may require a system restart or service reload. No official patch is currently indicated; mitigation relies on configuration changes.
Technical Details
- Gcve Source
- db.gcve.eu
- Csaf Category
- csaf_security_advisory
- Csaf Version
- 2.0
- Publisher
- Red Hat Product Security
- Advisory Id
- RHSA-2026:41136
- Cve Count
- 1
- Additional Cves
- []
- Cvss Version
- null
Threat ID: 6a81d6f4bf8831d53949f885
Added to database: 08/16/2026, 15:27:48 UTC
Last enriched: 08/16/2026, 15:28:51 UTC
Last updated: 08/16/2026, 20:41:00 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.