Поиск уязвимостей
Количество 26
Количество 26
CVE-2025-38100
In the Linux kernel, the following vulnerability has been resolved: x86/iopl: Cure TIF_IO_BITMAP inconsistencies io_bitmap_exit() is invoked from exit_thread() when a task exists or when a fork fails. In the latter case the exit_thread() cleans up resources which were allocated during fork(). io_bitmap_exit() invokes task_update_io_bitmap(), which in turn ends up in tss_update_io_bitmap(). tss_update_io_bitmap() operates on the current task. If current has TIF_IO_BITMAP set, but no bitmap installed, tss_update_io_bitmap() crashes with a NULL pointer dereference. There are two issues, which lead to that problem: 1) io_bitmap_exit() should not invoke task_update_io_bitmap() when the task, which is cleaned up, is not the current task. That's a clear indicator for a cleanup after a failed fork(). 2) A task should not have TIF_IO_BITMAP set and neither a bitmap installed nor IOPL emulation level 3 activated. This happens when a kernel thread is created in the context of a user space thre...
CVE-2025-38100
In the Linux kernel, the following vulnerability has been resolved: x86/iopl: Cure TIF_IO_BITMAP inconsistencies io_bitmap_exit() is invoked from exit_thread() when a task exists or when a fork fails. In the latter case the exit_thread() cleans up resources which were allocated during fork(). io_bitmap_exit() invokes task_update_io_bitmap(), which in turn ends up in tss_update_io_bitmap(). tss_update_io_bitmap() operates on the current task. If current has TIF_IO_BITMAP set, but no bitmap installed, tss_update_io_bitmap() crashes with a NULL pointer dereference. There are two issues, which lead to that problem: 1) io_bitmap_exit() should not invoke task_update_io_bitmap() when the task, which is cleaned up, is not the current task. That's a clear indicator for a cleanup after a failed fork(). 2) A task should not have TIF_IO_BITMAP set and neither a bitmap installed nor IOPL emulation level 3 activated. This happens when a kernel thread is created in the context of a user space thre...
CVE-2025-38100
In the Linux kernel, the following vulnerability has been resolved: x86/iopl: Cure TIF_IO_BITMAP inconsistencies io_bitmap_exit() is invoked from exit_thread() when a task exists or when a fork fails. In the latter case the exit_thread() cleans up resources which were allocated during fork(). io_bitmap_exit() invokes task_update_io_bitmap(), which in turn ends up in tss_update_io_bitmap(). tss_update_io_bitmap() operates on the current task. If current has TIF_IO_BITMAP set, but no bitmap installed, tss_update_io_bitmap() crashes with a NULL pointer dereference. There are two issues, which lead to that problem: 1) io_bitmap_exit() should not invoke task_update_io_bitmap() when the task, which is cleaned up, is not the current task. That's a clear indicator for a cleanup after a failed fork(). 2) A task should not have TIF_IO_BITMAP set and neither a bitmap installed nor IOPL emulation level 3 activated. This happens when a kernel thread is created in the
CVE-2025-38100
x86/iopl: Cure TIF_IO_BITMAP inconsistencies
CVE-2025-38100
In the Linux kernel, the following vulnerability has been resolved: x ...
GHSA-hhj3-j6pg-f7mv
In the Linux kernel, the following vulnerability has been resolved: x86/iopl: Cure TIF_IO_BITMAP inconsistencies io_bitmap_exit() is invoked from exit_thread() when a task exists or when a fork fails. In the latter case the exit_thread() cleans up resources which were allocated during fork(). io_bitmap_exit() invokes task_update_io_bitmap(), which in turn ends up in tss_update_io_bitmap(). tss_update_io_bitmap() operates on the current task. If current has TIF_IO_BITMAP set, but no bitmap installed, tss_update_io_bitmap() crashes with a NULL pointer dereference. There are two issues, which lead to that problem: 1) io_bitmap_exit() should not invoke task_update_io_bitmap() when the task, which is cleaned up, is not the current task. That's a clear indicator for a cleanup after a failed fork(). 2) A task should not have TIF_IO_BITMAP set and neither a bitmap installed nor IOPL emulation level 3 activated. This happens when a kernel thread is created in t...
BDU:2025-09025
Уязвимость функции io_bitmap_exit() ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20260323-80-0003
Уязвимость kernel-lt
ROS-20260323-73-0003
Уязвимость kernel-lt
ELSA-2025-20552
ELSA-2025-20552: Unbreakable Enterprise kernel security update (IMPORTANT)
ALT-PU-2025-16617
ALT-PU-2025-16617: package `kernel-image-rt` update to version 5.10.239-alt1.rt133
SUSE-SU-2025:03023-1
Security update for the Linux Kernel
SUSE-SU-2025:02996-1
Security update for the Linux Kernel
SUSE-SU-2025:02969-1
Security update for the Linux Kernel
ALT-PU-2025-16605
ALT-PU-2025-16605: package `kernel-image-std-def` update to version 5.10.240-alt1
SUSE-SU-2025:02853-1
Security update for the Linux Kernel
SUSE-SU-2025:02997-1
Security update for the Linux Kernel
SUSE-SU-2025:03011-1
Security update for the Linux Kernel
ELSA-2025-20551
ELSA-2025-20551: Unbreakable Enterprise kernel security update (IMPORTANT)
ALT-PU-2025-16596
ALT-PU-2025-16596: package `kernel-image-un-def` update to version 6.1.144-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2025-38100 In the Linux kernel, the following vulnerability has been resolved: x86/iopl: Cure TIF_IO_BITMAP inconsistencies io_bitmap_exit() is invoked from exit_thread() when a task exists or when a fork fails. In the latter case the exit_thread() cleans up resources which were allocated during fork(). io_bitmap_exit() invokes task_update_io_bitmap(), which in turn ends up in tss_update_io_bitmap(). tss_update_io_bitmap() operates on the current task. If current has TIF_IO_BITMAP set, but no bitmap installed, tss_update_io_bitmap() crashes with a NULL pointer dereference. There are two issues, which lead to that problem: 1) io_bitmap_exit() should not invoke task_update_io_bitmap() when the task, which is cleaned up, is not the current task. That's a clear indicator for a cleanup after a failed fork(). 2) A task should not have TIF_IO_BITMAP set and neither a bitmap installed nor IOPL emulation level 3 activated. This happens when a kernel thread is created in the context of a user space thre... | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
CVE-2025-38100 In the Linux kernel, the following vulnerability has been resolved: x86/iopl: Cure TIF_IO_BITMAP inconsistencies io_bitmap_exit() is invoked from exit_thread() when a task exists or when a fork fails. In the latter case the exit_thread() cleans up resources which were allocated during fork(). io_bitmap_exit() invokes task_update_io_bitmap(), which in turn ends up in tss_update_io_bitmap(). tss_update_io_bitmap() operates on the current task. If current has TIF_IO_BITMAP set, but no bitmap installed, tss_update_io_bitmap() crashes with a NULL pointer dereference. There are two issues, which lead to that problem: 1) io_bitmap_exit() should not invoke task_update_io_bitmap() when the task, which is cleaned up, is not the current task. That's a clear indicator for a cleanup after a failed fork(). 2) A task should not have TIF_IO_BITMAP set and neither a bitmap installed nor IOPL emulation level 3 activated. This happens when a kernel thread is created in the context of a user space thre... | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
CVE-2025-38100 In the Linux kernel, the following vulnerability has been resolved: x86/iopl: Cure TIF_IO_BITMAP inconsistencies io_bitmap_exit() is invoked from exit_thread() when a task exists or when a fork fails. In the latter case the exit_thread() cleans up resources which were allocated during fork(). io_bitmap_exit() invokes task_update_io_bitmap(), which in turn ends up in tss_update_io_bitmap(). tss_update_io_bitmap() operates on the current task. If current has TIF_IO_BITMAP set, but no bitmap installed, tss_update_io_bitmap() crashes with a NULL pointer dereference. There are two issues, which lead to that problem: 1) io_bitmap_exit() should not invoke task_update_io_bitmap() when the task, which is cleaned up, is not the current task. That's a clear indicator for a cleanup after a failed fork(). 2) A task should not have TIF_IO_BITMAP set and neither a bitmap installed nor IOPL emulation level 3 activated. This happens when a kernel thread is created in the | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
CVE-2025-38100 x86/iopl: Cure TIF_IO_BITMAP inconsistencies | CVSS3: 7 | 0% Низкий | больше 1 года назад | |
CVE-2025-38100 In the Linux kernel, the following vulnerability has been resolved: x ... | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
GHSA-hhj3-j6pg-f7mv In the Linux kernel, the following vulnerability has been resolved: x86/iopl: Cure TIF_IO_BITMAP inconsistencies io_bitmap_exit() is invoked from exit_thread() when a task exists or when a fork fails. In the latter case the exit_thread() cleans up resources which were allocated during fork(). io_bitmap_exit() invokes task_update_io_bitmap(), which in turn ends up in tss_update_io_bitmap(). tss_update_io_bitmap() operates on the current task. If current has TIF_IO_BITMAP set, but no bitmap installed, tss_update_io_bitmap() crashes with a NULL pointer dereference. There are two issues, which lead to that problem: 1) io_bitmap_exit() should not invoke task_update_io_bitmap() when the task, which is cleaned up, is not the current task. That's a clear indicator for a cleanup after a failed fork(). 2) A task should not have TIF_IO_BITMAP set and neither a bitmap installed nor IOPL emulation level 3 activated. This happens when a kernel thread is created in t... | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
BDU:2025-09025 Уязвимость функции io_bitmap_exit() ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
ROS-20260323-80-0003 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | 8 месяцев назад | |
ROS-20260323-73-0003 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | 8 месяцев назад | |
ELSA-2025-20552 ELSA-2025-20552: Unbreakable Enterprise kernel security update (IMPORTANT) | около 1 года назад | |||
ALT-PU-2025-16617 ALT-PU-2025-16617: package `kernel-image-rt` update to version 5.10.239-alt1.rt133 | CVSS3: 8 | больше 1 года назад | ||
SUSE-SU-2025:03023-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2025:02996-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2025:02969-1 Security update for the Linux Kernel | около 1 года назад | |||
ALT-PU-2025-16605 ALT-PU-2025-16605: package `kernel-image-std-def` update to version 5.10.240-alt1 | CVSS3: 8 | больше 1 года назад | ||
SUSE-SU-2025:02853-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2025:02997-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2025:03011-1 Security update for the Linux Kernel | около 1 года назад | |||
ELSA-2025-20551 ELSA-2025-20551: Unbreakable Enterprise kernel security update (IMPORTANT) | около 1 года назад | |||
ALT-PU-2025-16596 ALT-PU-2025-16596: package `kernel-image-un-def` update to version 6.1.144-alt1 | CVSS3: 9.3 | больше 1 года назад |
Уязвимостей на страницу