Количество 35
Количество 35

CVE-2024-43882
In the Linux kernel, the following vulnerability has been resolved: exec: Fix ToCToU between perm check and set-uid/gid usage When opening a file for exec via do_filp_open(), permission checking is done against the file's metadata at that moment, and on success, a file pointer is passed back. Much later in the execve() code path, the file metadata (specifically mode, uid, and gid) is used to determine if/how to set the uid and gid. However, those values may have changed since the permissions check, meaning the execution may gain unintended privileges. For example, if a file could change permissions from executable and not set-id: ---------x 1 root root 16048 Aug 7 13:16 target to set-id and non-executable: ---S------ 1 root root 16048 Aug 7 13:16 target it is possible to gain root privileges when execution should have been disallowed. While this race condition is rare in real-world scenarios, it has been observed (and proven exploitable) when package managers are updating ...

CVE-2024-43882
In the Linux kernel, the following vulnerability has been resolved: exec: Fix ToCToU between perm check and set-uid/gid usage When opening a file for exec via do_filp_open(), permission checking is done against the file's metadata at that moment, and on success, a file pointer is passed back. Much later in the execve() code path, the file metadata (specifically mode, uid, and gid) is used to determine if/how to set the uid and gid. However, those values may have changed since the permissions check, meaning the execution may gain unintended privileges. For example, if a file could change permissions from executable and not set-id: ---------x 1 root root 16048 Aug 7 13:16 target to set-id and non-executable: ---S------ 1 root root 16048 Aug 7 13:16 target it is possible to gain root privileges when execution should have been disallowed. While this race condition is rare in real-world scenarios, it has been observed (and proven exploitable) when package managers are updating the setu...

CVE-2024-43882
In the Linux kernel, the following vulnerability has been resolved: exec: Fix ToCToU between perm check and set-uid/gid usage When opening a file for exec via do_filp_open(), permission checking is done against the file's metadata at that moment, and on success, a file pointer is passed back. Much later in the execve() code path, the file metadata (specifically mode, uid, and gid) is used to determine if/how to set the uid and gid. However, those values may have changed since the permissions check, meaning the execution may gain unintended privileges. For example, if a file could change permissions from executable and not set-id: ---------x 1 root root 16048 Aug 7 13:16 target to set-id and non-executable: ---S------ 1 root root 16048 Aug 7 13:16 target it is possible to gain root privileges when execution should have been disallowed. While this race condition is rare in real-world scenarios, it has been observed (and proven exploitable) when package managers are updating the

CVE-2024-43882
CVE-2024-43882
In the Linux kernel, the following vulnerability has been resolved: e ...
GHSA-gpj2-qxrh-r55r
In the Linux kernel, the following vulnerability has been resolved: exec: Fix ToCToU between perm check and set-uid/gid usage When opening a file for exec via do_filp_open(), permission checking is done against the file's metadata at that moment, and on success, a file pointer is passed back. Much later in the execve() code path, the file metadata (specifically mode, uid, and gid) is used to determine if/how to set the uid and gid. However, those values may have changed since the permissions check, meaning the execution may gain unintended privileges. For example, if a file could change permissions from executable and not set-id: ---------x 1 root root 16048 Aug 7 13:16 target to set-id and non-executable: ---S------ 1 root root 16048 Aug 7 13:16 target it is possible to gain root privileges when execution should have been disallowed. While this race condition is rare in real-world scenarios, it has been observed (and proven exploitable) when package managers are updating ...

BDU:2024-09861
Уязвимость функции bprm_fill_uid() ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации

SUSE-SU-2025:01692-1
Security update for the Linux Kernel (Live Patch 17 for SLE 15 SP5)

SUSE-SU-2025:01676-1
Security update for the Linux Kernel (Live Patch 13 for SLE 15 SP5)

SUSE-SU-2025:01668-1
Security update for the Linux Kernel (Live Patch 12 for SLE 15 SP5)

SUSE-SU-2025:01655-1
Security update for the Linux Kernel (Live Patch 15 for SLE 15 SP5)

SUSE-SU-2025:01610-1
Security update for the Linux Kernel (Live Patch 45 for SLE 15 SP3)

SUSE-SU-2025:01590-1
Security update for the Linux Kernel (Live Patch 56 for SLE 12 SP5)

SUSE-SU-2025:01683-1
Security update for the Linux Kernel (Live Patch 3 for SLE 15 SP6)

SUSE-SU-2025:01675-1
Security update for the Linux Kernel (Live Patch 1 for SLE 15 SP6)

SUSE-SU-2025:01601-1
Security update for the Linux Kernel RT (Live Patch 0 for SLE 15 SP6)

SUSE-SU-2024:3467-1
Security update for the Linux Kernel

ROS-20250205-02
Множественные уязвимости kernel-lt

SUSE-SU-2024:3499-1
Security update for the Linux Kernel

SUSE-SU-2024:3249-1
Security update for the Linux Kernel
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
---|---|---|---|---|
![]() | CVE-2024-43882 In the Linux kernel, the following vulnerability has been resolved: exec: Fix ToCToU between perm check and set-uid/gid usage When opening a file for exec via do_filp_open(), permission checking is done against the file's metadata at that moment, and on success, a file pointer is passed back. Much later in the execve() code path, the file metadata (specifically mode, uid, and gid) is used to determine if/how to set the uid and gid. However, those values may have changed since the permissions check, meaning the execution may gain unintended privileges. For example, if a file could change permissions from executable and not set-id: ---------x 1 root root 16048 Aug 7 13:16 target to set-id and non-executable: ---S------ 1 root root 16048 Aug 7 13:16 target it is possible to gain root privileges when execution should have been disallowed. While this race condition is rare in real-world scenarios, it has been observed (and proven exploitable) when package managers are updating ... | CVSS3: 7 | 0% Низкий | 10 месяцев назад |
![]() | CVE-2024-43882 In the Linux kernel, the following vulnerability has been resolved: exec: Fix ToCToU between perm check and set-uid/gid usage When opening a file for exec via do_filp_open(), permission checking is done against the file's metadata at that moment, and on success, a file pointer is passed back. Much later in the execve() code path, the file metadata (specifically mode, uid, and gid) is used to determine if/how to set the uid and gid. However, those values may have changed since the permissions check, meaning the execution may gain unintended privileges. For example, if a file could change permissions from executable and not set-id: ---------x 1 root root 16048 Aug 7 13:16 target to set-id and non-executable: ---S------ 1 root root 16048 Aug 7 13:16 target it is possible to gain root privileges when execution should have been disallowed. While this race condition is rare in real-world scenarios, it has been observed (and proven exploitable) when package managers are updating the setu... | CVSS3: 7 | 0% Низкий | 10 месяцев назад |
![]() | CVE-2024-43882 In the Linux kernel, the following vulnerability has been resolved: exec: Fix ToCToU between perm check and set-uid/gid usage When opening a file for exec via do_filp_open(), permission checking is done against the file's metadata at that moment, and on success, a file pointer is passed back. Much later in the execve() code path, the file metadata (specifically mode, uid, and gid) is used to determine if/how to set the uid and gid. However, those values may have changed since the permissions check, meaning the execution may gain unintended privileges. For example, if a file could change permissions from executable and not set-id: ---------x 1 root root 16048 Aug 7 13:16 target to set-id and non-executable: ---S------ 1 root root 16048 Aug 7 13:16 target it is possible to gain root privileges when execution should have been disallowed. While this race condition is rare in real-world scenarios, it has been observed (and proven exploitable) when package managers are updating the | CVSS3: 7 | 0% Низкий | 10 месяцев назад |
![]() | CVSS3: 7 | 0% Низкий | 8 месяцев назад | |
CVE-2024-43882 In the Linux kernel, the following vulnerability has been resolved: e ... | CVSS3: 7 | 0% Низкий | 10 месяцев назад | |
GHSA-gpj2-qxrh-r55r In the Linux kernel, the following vulnerability has been resolved: exec: Fix ToCToU between perm check and set-uid/gid usage When opening a file for exec via do_filp_open(), permission checking is done against the file's metadata at that moment, and on success, a file pointer is passed back. Much later in the execve() code path, the file metadata (specifically mode, uid, and gid) is used to determine if/how to set the uid and gid. However, those values may have changed since the permissions check, meaning the execution may gain unintended privileges. For example, if a file could change permissions from executable and not set-id: ---------x 1 root root 16048 Aug 7 13:16 target to set-id and non-executable: ---S------ 1 root root 16048 Aug 7 13:16 target it is possible to gain root privileges when execution should have been disallowed. While this race condition is rare in real-world scenarios, it has been observed (and proven exploitable) when package managers are updating ... | CVSS3: 7 | 0% Низкий | 10 месяцев назад | |
![]() | BDU:2024-09861 Уязвимость функции bprm_fill_uid() ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации | CVSS3: 7 | 0% Низкий | 10 месяцев назад |
![]() | SUSE-SU-2025:01692-1 Security update for the Linux Kernel (Live Patch 17 for SLE 15 SP5) | 27 дней назад | ||
![]() | SUSE-SU-2025:01676-1 Security update for the Linux Kernel (Live Patch 13 for SLE 15 SP5) | 28 дней назад | ||
![]() | SUSE-SU-2025:01668-1 Security update for the Linux Kernel (Live Patch 12 for SLE 15 SP5) | 28 дней назад | ||
![]() | SUSE-SU-2025:01655-1 Security update for the Linux Kernel (Live Patch 15 for SLE 15 SP5) | 28 дней назад | ||
![]() | SUSE-SU-2025:01610-1 Security update for the Linux Kernel (Live Patch 45 for SLE 15 SP3) | 29 дней назад | ||
![]() | SUSE-SU-2025:01590-1 Security update for the Linux Kernel (Live Patch 56 for SLE 12 SP5) | около 1 месяца назад | ||
![]() | SUSE-SU-2025:01683-1 Security update for the Linux Kernel (Live Patch 3 for SLE 15 SP6) | 28 дней назад | ||
![]() | SUSE-SU-2025:01675-1 Security update for the Linux Kernel (Live Patch 1 for SLE 15 SP6) | 28 дней назад | ||
![]() | SUSE-SU-2025:01601-1 Security update for the Linux Kernel RT (Live Patch 0 for SLE 15 SP6) | около 1 месяца назад | ||
![]() | SUSE-SU-2024:3467-1 Security update for the Linux Kernel | 9 месяцев назад | ||
![]() | ROS-20250205-02 Множественные уязвимости kernel-lt | CVSS3: 7.8 | 4 месяца назад | |
![]() | SUSE-SU-2024:3499-1 Security update for the Linux Kernel | 9 месяцев назад | ||
![]() | SUSE-SU-2024:3249-1 Security update for the Linux Kernel | 9 месяцев назад |
Уязвимостей на страницу