Количество 72
Количество 72
GHSA-p8xh-x6wj-7w7g
In the Linux kernel, the following vulnerability has been resolved: drm/gem: Acquire references on GEM handles for framebuffers A GEM handle can be released while the GEM buffer object is attached to a DRM framebuffer. This leads to the release of the dma-buf backing the buffer object, if any. [1] Trying to use the framebuffer in further mode-setting operations leads to a segmentation fault. Most easily happens with driver that use shadow planes for vmap-ing the dma-buf during a page flip. An example is shown below. [ 156.791968] ------------[ cut here ]------------ [ 156.796830] WARNING: CPU: 2 PID: 2255 at drivers/dma-buf/dma-buf.c:1527 dma_buf_vmap+0x224/0x430 [...] [ 156.942028] RIP: 0010:dma_buf_vmap+0x224/0x430 [ 157.043420] Call Trace: [ 157.045898] <TASK> [ 157.048030] ? show_trace_log_lvl+0x1af/0x2c0 [ 157.052436] ? show_trace_log_lvl+0x1af/0x2c0 [ 157.056836] ? show_trace_log_lvl+0x1af/0x2c0 [ 157.061253] ? drm_gem_shmem_vmap+0x74/0x710 [ 157.065567] ? d...
BDU:2025-09233
Уязвимость функции dma_buf_vmap() ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ELSA-2025-15782
ELSA-2025-15782: kernel security update (MODERATE)
RLSA-2025:15662
Important: kernel security update
GHSA-mr4j-mh66-4679
In the Linux kernel, the following vulnerability has been resolved: posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() If an exiting non-autoreaping task has already passed exit_notify() and calls handle_posix_cpu_timers() from IRQ, it can be reaped by its parent or debugger right after unlock_task_sighand(). If a concurrent posix_cpu_timer_del() runs at that moment, it won't be able to detect timer->it.cpu.firing != 0: cpu_timer_task_rcu() and/or lock_task_sighand() will fail. Add the tsk->exit_state check into run_posix_cpu_timers() to fix this. This fix is not needed if CONFIG_POSIX_CPU_TIMERS_TASK_WORK=y, because exit_task_work() is called before exit_notify(). But the check still makes sense, task_work_add(&tsk->posix_cputimers_work.work) will fail anyway in this case.
ELSA-2025-15662
ELSA-2025-15662: kernel security update (IMPORTANT)
BDU:2025-10870
Уязвимость функции handle_posix_cpu_timers ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
SUSE-SU-2025:01620-1
Security update for the Linux Kernel
SUSE-SU-2025:02923-1
Security update for the Linux Kernel
RLSA-2025:15471
Important: kernel security update
ELSA-2025-15471
ELSA-2025-15471: kernel security update (IMPORTANT)
ELSA-2025-20552
ELSA-2025-20552: Unbreakable Enterprise kernel security update (IMPORTANT)
SUSE-SU-2025:03204-1
Security update for the Linux Kernel
openSUSE-SU-2025:20081-1
Security update for the Linux Kernel
openSUSE-SU-2025-20011-1
Security update for the Linux Kernel
ELSA-2025-15785
ELSA-2025-15785: kernel security update (IMPORTANT)
ELSA-2025-20518-0
ELSA-2025-20518-0: kernel security update (MODERATE)
RLSA-2025:20518
Moderate: kernel security update
SUSE-SU-2025:01972-1
Security update for the Linux Kernel
SUSE-SU-2025:01707-1
Security update for the Linux Kernel
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
GHSA-p8xh-x6wj-7w7g In the Linux kernel, the following vulnerability has been resolved: drm/gem: Acquire references on GEM handles for framebuffers A GEM handle can be released while the GEM buffer object is attached to a DRM framebuffer. This leads to the release of the dma-buf backing the buffer object, if any. [1] Trying to use the framebuffer in further mode-setting operations leads to a segmentation fault. Most easily happens with driver that use shadow planes for vmap-ing the dma-buf during a page flip. An example is shown below. [ 156.791968] ------------[ cut here ]------------ [ 156.796830] WARNING: CPU: 2 PID: 2255 at drivers/dma-buf/dma-buf.c:1527 dma_buf_vmap+0x224/0x430 [...] [ 156.942028] RIP: 0010:dma_buf_vmap+0x224/0x430 [ 157.043420] Call Trace: [ 157.045898] <TASK> [ 157.048030] ? show_trace_log_lvl+0x1af/0x2c0 [ 157.052436] ? show_trace_log_lvl+0x1af/0x2c0 [ 157.056836] ? show_trace_log_lvl+0x1af/0x2c0 [ 157.061253] ? drm_gem_shmem_vmap+0x74/0x710 [ 157.065567] ? d... | CVSS3: 5.5 | 0% Низкий | 5 месяцев назад | |
BDU:2025-09233 Уязвимость функции dma_buf_vmap() ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 7 | 0% Низкий | 6 месяцев назад | |
ELSA-2025-15782 ELSA-2025-15782: kernel security update (MODERATE) | 3 месяца назад | |||
RLSA-2025:15662 Important: kernel security update | 0% Низкий | 3 месяца назад | ||
GHSA-mr4j-mh66-4679 In the Linux kernel, the following vulnerability has been resolved: posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() If an exiting non-autoreaping task has already passed exit_notify() and calls handle_posix_cpu_timers() from IRQ, it can be reaped by its parent or debugger right after unlock_task_sighand(). If a concurrent posix_cpu_timer_del() runs at that moment, it won't be able to detect timer->it.cpu.firing != 0: cpu_timer_task_rcu() and/or lock_task_sighand() will fail. Add the tsk->exit_state check into run_posix_cpu_timers() to fix this. This fix is not needed if CONFIG_POSIX_CPU_TIMERS_TASK_WORK=y, because exit_task_work() is called before exit_notify(). But the check still makes sense, task_work_add(&tsk->posix_cputimers_work.work) will fail anyway in this case. | CVSS3: 7.4 | 0% Низкий | 5 месяцев назад | |
ELSA-2025-15662 ELSA-2025-15662: kernel security update (IMPORTANT) | 3 месяца назад | |||
BDU:2025-10870 Уязвимость функции handle_posix_cpu_timers ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 4.6 | 0% Низкий | 5 месяцев назад | |
SUSE-SU-2025:01620-1 Security update for the Linux Kernel | 7 месяцев назад | |||
SUSE-SU-2025:02923-1 Security update for the Linux Kernel | 4 месяца назад | |||
RLSA-2025:15471 Important: kernel security update | 3 месяца назад | |||
ELSA-2025-15471 ELSA-2025-15471: kernel security update (IMPORTANT) | 3 месяца назад | |||
ELSA-2025-20552 ELSA-2025-20552: Unbreakable Enterprise kernel security update (IMPORTANT) | 3 месяца назад | |||
SUSE-SU-2025:03204-1 Security update for the Linux Kernel | 3 месяца назад | |||
openSUSE-SU-2025:20081-1 Security update for the Linux Kernel | 25 дней назад | |||
openSUSE-SU-2025-20011-1 Security update for the Linux Kernel | около 1 месяца назад | |||
ELSA-2025-15785 ELSA-2025-15785: kernel security update (IMPORTANT) | 3 месяца назад | |||
ELSA-2025-20518-0 ELSA-2025-20518-0: kernel security update (MODERATE) | около 1 месяца назад | |||
RLSA-2025:20518 Moderate: kernel security update | 28 дней назад | |||
SUSE-SU-2025:01972-1 Security update for the Linux Kernel | 6 месяцев назад | |||
SUSE-SU-2025:01707-1 Security update for the Linux Kernel | 7 месяцев назад |
Уязвимостей на страницу