Поиск уязвимостей
Количество 17
Количество 17
GHSA-6766-cx7r-c5q6
`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...
CVE-2026-72693
`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...
CVE-2026-72693
`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...
CVE-2026-72693
`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
CVE-2026-72693
Kbd: local privilege escalation in openvt via incorrect process owner verification allowing passwordless root login
CVE-2026-72693
`openvt -u` is intended to identify the owner of the current VT and th ...
openSUSE-SU-2026:21939-1
Security update for kbd
SUSE-SU-2026:4211-1
Security update for kbd
SUSE-SU-2026:4207-1
Security update for kbd
ROS-20261110-80-0176
Уязвимость kbd
ROS-20261110-73-0177
Уязвимость kbd
RLSA-2026:78951
Moderate: kbd security update
RLSA-2026:57610
Moderate: kbd security update
RLSA-2026:57597
Moderate: kbd security update
ELSA-2026-78951
ELSA-2026-78951: kbd security update (MODERATE)
ELSA-2026-57610
ELSA-2026-57610: kbd security update (MODERATE)
ELSA-2026-57597
ELSA-2026-57597: kbd security update (MODERATE)
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
GHSA-6766-cx7r-c5q6 `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 | 0% Низкий | 3 месяца назад | |
CVE-2026-72693 `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 | 0% Низкий | 3 месяца назад | |
CVE-2026-72693 `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 | 0% Низкий | 3 месяца назад | |
CVE-2026-72693 `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 | 0% Низкий | 3 месяца назад | |
CVE-2026-72693 Kbd: local privilege escalation in openvt via incorrect process owner verification allowing passwordless root login | CVSS3: 7.8 | 0% Низкий | 3 месяца назад | |
CVE-2026-72693 `openvt -u` is intended to identify the owner of the current VT and th ... | CVSS3: 7.8 | 0% Низкий | 3 месяца назад | |
openSUSE-SU-2026:21939-1 Security update for kbd | 0% Низкий | около 2 месяцев назад | ||
SUSE-SU-2026:4211-1 Security update for kbd | 0% Низкий | 2 месяца назад | ||
SUSE-SU-2026:4207-1 Security update for kbd | 0% Низкий | 2 месяца назад | ||
ROS-20261110-80-0176 Уязвимость kbd | CVSS3: 7.8 | 0% Низкий | 9 дней назад | |
ROS-20261110-73-0177 Уязвимость kbd | CVSS3: 7.8 | 0% Низкий | 9 дней назад | |
RLSA-2026:78951 Moderate: kbd security update | 0% Низкий | около 1 месяца назад | ||
RLSA-2026:57610 Moderate: kbd security update | 0% Низкий | 3 месяца назад | ||
RLSA-2026:57597 Moderate: kbd security update | 0% Низкий | 3 месяца назад | ||
ELSA-2026-78951 ELSA-2026-78951: kbd security update (MODERATE) | 0% Низкий | около 1 месяца назад | ||
ELSA-2026-57610 ELSA-2026-57610: kbd security update (MODERATE) | 0% Низкий | 3 месяца назад | ||
ELSA-2026-57597 ELSA-2026-57597: kbd security update (MODERATE) | 0% Низкий | 3 месяца назад |
Уязвимостей на страницу