Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

oracle-oval логотип

ELSA-2026-78951

Опубликовано: 08 окт. 2026
Источник: oracle-oval
Платформа: Oracle Linux 8

Описание

ELSA-2026-78951: kbd security update (MODERATE)

[2.0.4-11.1]

  • Fix CVE-2026-72693: openvt -u process matching more conservative Resolves: RHEL-235979

Обновленные пакеты

Oracle Linux 8

Oracle Linux aarch64

kbd

2.0.4-11.el8_10.1

kbd-legacy

2.0.4-11.el8_10.1

kbd-misc

2.0.4-11.el8_10.1

Oracle Linux x86_64

kbd

2.0.4-11.el8_10.1

kbd-legacy

2.0.4-11.el8_10.1

kbd-misc

2.0.4-11.el8_10.1

Связанные CVE

Связанные уязвимости

CVSS3: 7.8
ubuntu
3 месяца назад

`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 depl...

CVSS3: 7.8
redhat
3 месяца назад

`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 depl...

CVSS3: 7.8
nvd
3 месяца назад

`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 deploym

CVSS3: 7.8
msrc
3 месяца назад

Kbd: local privilege escalation in openvt via incorrect process owner verification allowing passwordless root login

CVSS3: 7.8
debian
3 месяца назад

`openvt -u` is intended to identify the owner of the current VT and th ...