Description
`openvt -u` is intended to identify the owner of the current VT and then execute `login` as that user from a privileged context. In the documented `kbrequest`/init usage, the ownership test in `authenticate_user()` relies on `stat("/proc/<pid>/fd/0")`. `stat()` on `/proc/<pid>/fd/0` follows the symlink to the underlying TTY device node. As a result, `buf.st_uid` reflects the owner of the TTY node rather than the owner of the process holding the file descriptor. If the TTY owner returns to `root` or the getty owner after logout while an unprivileged process still has `fd 0` attached to that TTY, the check can incorrectly treat that process as belonging to the privileged console owner. Once that check succeeds, the `-u` path executes a passwordless login as the selected user. In the documented `kbrequest`/init deployment using `openvt -us`, this can result in passwordless `login -f root` on the spawned VT. This report establishes that privilege escalation path for that documented deployment; it does not claim equivalent reachability for deployments that do not use `openvt -u` from a privileged `kbrequest`/init path.
Published: 2026-08-11
Score: 7.8 High
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

openvt -u is supposed to identify the console owner and then start a login session as that user from a privileged context. The underlying check incorrectly uses stat on /proc/<pid>/fd/0, which resolves to the TTY device node and reports its owner instead of the process owner. This flaw allows an attacker who can keep an unprivileged process attached to a root-owned TTY after logout to fool the check into thinking the process is privileged, permitting a passwordless login as root. The vulnerability results in local privilege escalation and fulfills CWE-284: Improper Access Control.

Affected Systems

Affected products include Red Hat Enterprise Linux 10, 6, 7, 8, and 9, Red Hat Hardened Images, and Red Hat OpenShift Container Platform 4. All versions of these listings are impacted because the issue resides in the openvt utility shipped with these distributions; no version pinning was provided in the advisory.

Risk and Exploitability

The CVSS score of 7.8 indicates a high severity for local privilege escalation, but the EPSS score is not available, and the flaw is not currently listed in CISA KEV. The attack path requires privileged kbrequest/init deployments that invoke openvt -u; an attacker would need to execute or influence an unprivileged process holding the root TTY, then trigger the faulty ownership test. Once the test succeeds, a passwordless login -f root is started, giving full system control. Because the flaw is limited to the specific kbrequest/init scenario, the risk to systems that do not use this deployment path is lower.

Generated by OpenCVE AI on August 11, 2026 at 10:26 UTC.

Remediation

Vendor Workaround

To mitigate this issue, avoid using `openvt -u` in privileged `kbrequest`/init deployments. Instead, configure the keyboard request 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 to take effect.


OpenCVE Recommended Actions

  • Disable or remove the use of openvt -u in privileged kbrequest/init or keyboard request bindings.
  • Reconfigure the keyboard request to initiate a standard authenticated login on the new virtual terminal, or disable the binding completely until a proper fix is released.
  • Keep the Red Hat system updated with the latest security patches and monitor Red Hat advisories for a permanent fix.

Generated by OpenCVE AI on August 11, 2026 at 10:26 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 11 Aug 2026 09:00:00 +0000

Type Values Removed Values Added
Description `openvt -u` is intended to identify the owner of the current VT and then execute `login` as that user from a privileged context. In the documented `kbrequest`/init usage, the ownership test in `authenticate_user()` relies on `stat("/proc/<pid>/fd/0")`. `stat()` on `/proc/<pid>/fd/0` follows the symlink to the underlying TTY device node. As a result, `buf.st_uid` reflects the owner of the TTY node rather than the owner of the process holding the file descriptor. If the TTY owner returns to `root` or the getty owner after logout while an unprivileged process still has `fd 0` attached to that TTY, the check can incorrectly treat that process as belonging to the privileged console owner. Once that check succeeds, the `-u` path executes a passwordless login as the selected user. In the documented `kbrequest`/init deployment using `openvt -us`, this can result in passwordless `login -f root` on the spawned VT. This report establishes that privilege escalation path for that documented deployment; it does not claim equivalent reachability for deployments that do not use `openvt -u` from a privileged `kbrequest`/init path.
Title Kbd: local privilege escalation in openvt via incorrect process owner verification allowing passwordless root login
First Time appeared Redhat
Redhat enterprise Linux
Redhat hummingbird
Redhat openshift
Weaknesses CWE-284
CPEs cpe:/a:redhat:hummingbird:1
cpe:/a:redhat:openshift:4
cpe:/o:redhat:enterprise_linux:10
cpe:/o:redhat:enterprise_linux:6
cpe:/o:redhat:enterprise_linux:7
cpe:/o:redhat:enterprise_linux:8
cpe:/o:redhat:enterprise_linux:9
Vendors & Products Redhat
Redhat enterprise Linux
Redhat hummingbird
Redhat openshift
References
Metrics cvssV3_1

{'score': 7.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}


Subscriptions

Redhat Enterprise Linux Hummingbird Openshift
cve-icon MITRE

Status: PUBLISHED

Assigner: redhat

Published:

Updated: 2026-08-11T08:39:24.983Z

Reserved: 2026-08-10T12:35:16.746Z

Link: CVE-2026-72693

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-11T10:30:04Z

Weaknesses