Поиск уязвимостей
Количество 16
Количество 16
CVE-2024-46845
In the Linux kernel, the following vulnerability has been resolved: tracing/timerlat: Only clear timer if a kthread exists The timerlat tracer can use user space threads to check for osnoise and timer latency. If the program using this is killed via a SIGTERM, the threads are shutdown one at a time and another tracing instance can start up resetting the threads before they are fully closed. That causes the hrtimer assigned to the kthread to be shutdown and freed twice when the dying thread finally closes the file descriptors, causing a use-after-free bug. Only cancel the hrtimer if the associated thread is still around. Also add the interface_lock around the resetting of the tlat_var->kthread. Note, this is just a quick fix that can be backported to stable. A real fix is to have a better synchronization between the shutdown of old threads and the starting of new ones.
CVE-2024-46845
In the Linux kernel, the following vulnerability has been resolved: tracing/timerlat: Only clear timer if a kthread exists The timerlat tracer can use user space threads to check for osnoise and timer latency. If the program using this is killed via a SIGTERM, the threads are shutdown one at a time and another tracing instance can start up resetting the threads before they are fully closed. That causes the hrtimer assigned to the kthread to be shutdown and freed twice when the dying thread finally closes the file descriptors, causing a use-after-free bug. Only cancel the hrtimer if the associated thread is still around. Also add the interface_lock around the resetting of the tlat_var->kthread. Note, this is just a quick fix that can be backported to stable. A real fix is to have a better synchronization between the shutdown of old threads and the starting of new ones.
CVE-2024-46845
In the Linux kernel, the following vulnerability has been resolved: tracing/timerlat: Only clear timer if a kthread exists The timerlat tracer can use user space threads to check for osnoise and timer latency. If the program using this is killed via a SIGTERM, the threads are shutdown one at a time and another tracing instance can start up resetting the threads before they are fully closed. That causes the hrtimer assigned to the kthread to be shutdown and freed twice when the dying thread finally closes the file descriptors, causing a use-after-free bug. Only cancel the hrtimer if the associated thread is still around. Also add the interface_lock around the resetting of the tlat_var->kthread. Note, this is just a quick fix that can be backported to stable. A real fix is to have a better synchronization between the shutdown of old threads and the starting of new ones.
CVE-2024-46845
tracing/timerlat: Only clear timer if a kthread exists
CVE-2024-46845
In the Linux kernel, the following vulnerability has been resolved: t ...
GHSA-gvp7-4cxg-vpqq
In the Linux kernel, the following vulnerability has been resolved: tracing/timerlat: Only clear timer if a kthread exists The timerlat tracer can use user space threads to check for osnoise and timer latency. If the program using this is killed via a SIGTERM, the threads are shutdown one at a time and another tracing instance can start up resetting the threads before they are fully closed. That causes the hrtimer assigned to the kthread to be shutdown and freed twice when the dying thread finally closes the file descriptors, causing a use-after-free bug. Only cancel the hrtimer if the associated thread is still around. Also add the interface_lock around the resetting of the tlat_var->kthread. Note, this is just a quick fix that can be backported to stable. A real fix is to have a better synchronization between the shutdown of old threads and the starting of new ones.
BDU:2024-08299
Уязвимость функции tlat_var_reset() ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2024-08233
Уязвимость функции axg_card_add_tdm_loopback() ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
ROS-20241009-03
Множественные уязвимости kernel-lt
SUSE-SU-2024:4316-1
Security update for the Linux Kernel
SUSE-SU-2024:4314-1
Security update for the Linux Kernel
ALT-PU-2024-12968
ALT-PU-2024-12968: package `kernel-image-un-def` update to version 6.6.52-alt0.p11.1
SUSE-SU-2024:4387-1
Security update for the Linux Kernel
SUSE-SU-2024:4318-1
Security update for the Linux Kernel
ALT-PU-2024-13260
ALT-PU-2024-13260: package `kernel-image-pine` update to version 6.10.11-alt1
ALT-PU-2024-13979
ALT-PU-2024-13979: package `kernel-image-rpi-un` update to version 6.6.56-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2024-46845 In the Linux kernel, the following vulnerability has been resolved: tracing/timerlat: Only clear timer if a kthread exists The timerlat tracer can use user space threads to check for osnoise and timer latency. If the program using this is killed via a SIGTERM, the threads are shutdown one at a time and another tracing instance can start up resetting the threads before they are fully closed. That causes the hrtimer assigned to the kthread to be shutdown and freed twice when the dying thread finally closes the file descriptors, causing a use-after-free bug. Only cancel the hrtimer if the associated thread is still around. Also add the interface_lock around the resetting of the tlat_var->kthread. Note, this is just a quick fix that can be backported to stable. A real fix is to have a better synchronization between the shutdown of old threads and the starting of new ones. | CVSS3: 7.8 | 0% Низкий | около 2 лет назад | |
CVE-2024-46845 In the Linux kernel, the following vulnerability has been resolved: tracing/timerlat: Only clear timer if a kthread exists The timerlat tracer can use user space threads to check for osnoise and timer latency. If the program using this is killed via a SIGTERM, the threads are shutdown one at a time and another tracing instance can start up resetting the threads before they are fully closed. That causes the hrtimer assigned to the kthread to be shutdown and freed twice when the dying thread finally closes the file descriptors, causing a use-after-free bug. Only cancel the hrtimer if the associated thread is still around. Also add the interface_lock around the resetting of the tlat_var->kthread. Note, this is just a quick fix that can be backported to stable. A real fix is to have a better synchronization between the shutdown of old threads and the starting of new ones. | CVSS3: 4.1 | 0% Низкий | около 2 лет назад | |
CVE-2024-46845 In the Linux kernel, the following vulnerability has been resolved: tracing/timerlat: Only clear timer if a kthread exists The timerlat tracer can use user space threads to check for osnoise and timer latency. If the program using this is killed via a SIGTERM, the threads are shutdown one at a time and another tracing instance can start up resetting the threads before they are fully closed. That causes the hrtimer assigned to the kthread to be shutdown and freed twice when the dying thread finally closes the file descriptors, causing a use-after-free bug. Only cancel the hrtimer if the associated thread is still around. Also add the interface_lock around the resetting of the tlat_var->kthread. Note, this is just a quick fix that can be backported to stable. A real fix is to have a better synchronization between the shutdown of old threads and the starting of new ones. | CVSS3: 7.8 | 0% Низкий | около 2 лет назад | |
CVE-2024-46845 tracing/timerlat: Only clear timer if a kthread exists | CVSS3: 7.8 | 0% Низкий | около 2 лет назад | |
CVE-2024-46845 In the Linux kernel, the following vulnerability has been resolved: t ... | CVSS3: 7.8 | 0% Низкий | около 2 лет назад | |
GHSA-gvp7-4cxg-vpqq In the Linux kernel, the following vulnerability has been resolved: tracing/timerlat: Only clear timer if a kthread exists The timerlat tracer can use user space threads to check for osnoise and timer latency. If the program using this is killed via a SIGTERM, the threads are shutdown one at a time and another tracing instance can start up resetting the threads before they are fully closed. That causes the hrtimer assigned to the kthread to be shutdown and freed twice when the dying thread finally closes the file descriptors, causing a use-after-free bug. Only cancel the hrtimer if the associated thread is still around. Also add the interface_lock around the resetting of the tlat_var->kthread. Note, this is just a quick fix that can be backported to stable. A real fix is to have a better synchronization between the shutdown of old threads and the starting of new ones. | CVSS3: 7.8 | 0% Низкий | около 2 лет назад | |
BDU:2024-08299 Уязвимость функции tlat_var_reset() ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации | CVSS3: 7.8 | 0% Низкий | около 2 лет назад | |
BDU:2024-08233 Уязвимость функции axg_card_add_tdm_loopback() ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации | CVSS3: 7.8 | 0% Низкий | около 2 лет назад | |
ROS-20241009-03 Множественные уязвимости kernel-lt | CVSS3: 7.8 | около 2 лет назад | ||
SUSE-SU-2024:4316-1 Security update for the Linux Kernel | почти 2 года назад | |||
SUSE-SU-2024:4314-1 Security update for the Linux Kernel | почти 2 года назад | |||
ALT-PU-2024-12968 ALT-PU-2024-12968: package `kernel-image-un-def` update to version 6.6.52-alt0.p11.1 | CVSS3: 8.8 | около 2 лет назад | ||
SUSE-SU-2024:4387-1 Security update for the Linux Kernel | почти 2 года назад | |||
SUSE-SU-2024:4318-1 Security update for the Linux Kernel | почти 2 года назад | |||
ALT-PU-2024-13260 ALT-PU-2024-13260: package `kernel-image-pine` update to version 6.10.11-alt1 | CVSS3: 8.8 | около 2 лет назад | ||
ALT-PU-2024-13979 ALT-PU-2024-13979: package `kernel-image-rpi-un` update to version 6.6.56-alt1 | CVSS3: 7.8 | около 2 лет назад |
Уязвимостей на страницу