CVE-2026-72693
`openvt -u` is intended to identify the owner of the current VT and …
`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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- access.redhat.com/security/cve/CVE-2026-72693
- bugzilla.redhat.com/show_bug.cgi?id=2462115
- access.redhat.com/errata/RHSA-2026:41136
- access.redhat.com/errata/RHSA-2026:57597
- access.redhat.com/errata/RHSA-2026:57610
- access.redhat.com/errata/RHSA-2026:60440
- access.redhat.com/errata/RHSA-2026:66357
- access.redhat.com/errata/RHSA-2026:78951
- nvd.nist.gov/vuln/detail/CVE-2026-72693
- cve.org/CVERecord?id=CVE-2026-72693
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.