Количество 17
Количество 17
GHSA-qrpm-p5hj-4xg3
In the Linux kernel, the following vulnerability has been resolved: serial: max3100: Lock port->lock when calling uart_handle_cts_change() uart_handle_cts_change() has to be called with port lock taken, Since we run it in a separate work, the lock may not be taken at the time of running. Make sure that it's taken by explicitly doing that. Without it we got a splat: WARNING: CPU: 0 PID: 10 at drivers/tty/serial/serial_core.c:3491 uart_handle_cts_change+0xa6/0xb0 ... Workqueue: max3100-0 max3100_work [max3100] RIP: 0010:uart_handle_cts_change+0xa6/0xb0 ... max3100_handlerx+0xc5/0x110 [max3100] max3100_work+0x12a/0x340 [max3100]
CVE-2024-38634
In the Linux kernel, the following vulnerability has been resolved: serial: max3100: Lock port->lock when calling uart_handle_cts_change() uart_handle_cts_change() has to be called with port lock taken, Since we run it in a separate work, the lock may not be taken at the time of running. Make sure that it's taken by explicitly doing that. Without it we got a splat: WARNING: CPU: 0 PID: 10 at drivers/tty/serial/serial_core.c:3491 uart_handle_cts_change+0xa6/0xb0 ... Workqueue: max3100-0 max3100_work [max3100] RIP: 0010:uart_handle_cts_change+0xa6/0xb0 ... max3100_handlerx+0xc5/0x110 [max3100] max3100_work+0x12a/0x340 [max3100]
CVE-2024-38634
In the Linux kernel, the following vulnerability has been resolved: serial: max3100: Lock port->lock when calling uart_handle_cts_change() uart_handle_cts_change() has to be called with port lock taken, Since we run it in a separate work, the lock may not be taken at the time of running. Make sure that it's taken by explicitly doing that. Without it we got a splat: WARNING: CPU: 0 PID: 10 at drivers/tty/serial/serial_core.c:3491 uart_handle_cts_change+0xa6/0xb0 ... Workqueue: max3100-0 max3100_work [max3100] RIP: 0010:uart_handle_cts_change+0xa6/0xb0 ... max3100_handlerx+0xc5/0x110 [max3100] max3100_work+0x12a/0x340 [max3100]
CVE-2024-38634
In the Linux kernel, the following vulnerability has been resolved: serial: max3100: Lock port->lock when calling uart_handle_cts_change() uart_handle_cts_change() has to be called with port lock taken, Since we run it in a separate work, the lock may not be taken at the time of running. Make sure that it's taken by explicitly doing that. Without it we got a splat: WARNING: CPU: 0 PID: 10 at drivers/tty/serial/serial_core.c:3491 uart_handle_cts_change+0xa6/0xb0 ... Workqueue: max3100-0 max3100_work [max3100] RIP: 0010:uart_handle_cts_change+0xa6/0xb0 ... max3100_handlerx+0xc5/0x110 [max3100] max3100_work+0x12a/0x340 [max3100]
CVE-2024-38634
In the Linux kernel, the following vulnerability has been resolved: s ...
BDU:2025-04185
Уязвимость компонента max3100.c ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20250113-05
Множественные уязвимости kernel-lt
ELSA-2024-12611
ELSA-2024-12611: Unbreakable Enterprise kernel security update (IMPORTANT)
ELSA-2024-12585
ELSA-2024-12585: Unbreakable Enterprise kernel-container security update (IMPORTANT)
ELSA-2024-12584
ELSA-2024-12584: Unbreakable Enterprise kernel-container security update (IMPORTANT)
ELSA-2024-12581
ELSA-2024-12581: Unbreakable Enterprise kernel security update (IMPORTANT)
SUSE-SU-2024:2394-1
Security update for the Linux Kernel
SUSE-SU-2024:2372-1
Security update for the Linux Kernel
SUSE-SU-2024:2571-1
Security update for the Linux Kernel
SUSE-SU-2024:2896-1
Security update for the Linux Kernel
SUSE-SU-2024:2939-1
Security update for the Linux Kernel
SUSE-SU-2024:2973-1
Security update for the Linux Kernel
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
| GHSA-qrpm-p5hj-4xg3 In the Linux kernel, the following vulnerability has been resolved: serial: max3100: Lock port->lock when calling uart_handle_cts_change() uart_handle_cts_change() has to be called with port lock taken, Since we run it in a separate work, the lock may not be taken at the time of running. Make sure that it's taken by explicitly doing that. Without it we got a splat: WARNING: CPU: 0 PID: 10 at drivers/tty/serial/serial_core.c:3491 uart_handle_cts_change+0xa6/0xb0 ... Workqueue: max3100-0 max3100_work [max3100] RIP: 0010:uart_handle_cts_change+0xa6/0xb0 ... max3100_handlerx+0xc5/0x110 [max3100] max3100_work+0x12a/0x340 [max3100] | 0% Низкий | 12 месяцев назад | |
 | CVE-2024-38634 In the Linux kernel, the following vulnerability has been resolved: serial: max3100: Lock port->lock when calling uart_handle_cts_change() uart_handle_cts_change() has to be called with port lock taken, Since we run it in a separate work, the lock may not be taken at the time of running. Make sure that it's taken by explicitly doing that. Without it we got a splat: WARNING: CPU: 0 PID: 10 at drivers/tty/serial/serial_core.c:3491 uart_handle_cts_change+0xa6/0xb0 ... Workqueue: max3100-0 max3100_work [max3100] RIP: 0010:uart_handle_cts_change+0xa6/0xb0 ... max3100_handlerx+0xc5/0x110 [max3100] max3100_work+0x12a/0x340 [max3100] | 0% Низкий | 12 месяцев назад | |
 | CVE-2024-38634 In the Linux kernel, the following vulnerability has been resolved: serial: max3100: Lock port->lock when calling uart_handle_cts_change() uart_handle_cts_change() has to be called with port lock taken, Since we run it in a separate work, the lock may not be taken at the time of running. Make sure that it's taken by explicitly doing that. Without it we got a splat: WARNING: CPU: 0 PID: 10 at drivers/tty/serial/serial_core.c:3491 uart_handle_cts_change+0xa6/0xb0 ... Workqueue: max3100-0 max3100_work [max3100] RIP: 0010:uart_handle_cts_change+0xa6/0xb0 ... max3100_handlerx+0xc5/0x110 [max3100] max3100_work+0x12a/0x340 [max3100] | CVSS3: 4.4 | 0% Низкий | 12 месяцев назад |
 | CVE-2024-38634 In the Linux kernel, the following vulnerability has been resolved: serial: max3100: Lock port->lock when calling uart_handle_cts_change() uart_handle_cts_change() has to be called with port lock taken, Since we run it in a separate work, the lock may not be taken at the time of running. Make sure that it's taken by explicitly doing that. Without it we got a splat: WARNING: CPU: 0 PID: 10 at drivers/tty/serial/serial_core.c:3491 uart_handle_cts_change+0xa6/0xb0 ... Workqueue: max3100-0 max3100_work [max3100] RIP: 0010:uart_handle_cts_change+0xa6/0xb0 ... max3100_handlerx+0xc5/0x110 [max3100] max3100_work+0x12a/0x340 [max3100] | 0% Низкий | 12 месяцев назад | |
| CVE-2024-38634 In the Linux kernel, the following vulnerability has been resolved: s ... | 0% Низкий | 12 месяцев назад | |
 | BDU:2025-04185 Уязвимость компонента max3100.c ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | около 1 года назад |
 | ROS-20250113-05 Множественные уязвимости kernel-lt | CVSS3: 9.8 | 5 месяцев назад | |
| ELSA-2024-12611 ELSA-2024-12611: Unbreakable Enterprise kernel security update (IMPORTANT) | 9 месяцев назад | ||
| ELSA-2024-12585 ELSA-2024-12585: Unbreakable Enterprise kernel-container security update (IMPORTANT) | 10 месяцев назад | ||
| ELSA-2024-12584 ELSA-2024-12584: Unbreakable Enterprise kernel-container security update (IMPORTANT) | 10 месяцев назад | ||
| ELSA-2024-12581 ELSA-2024-12581: Unbreakable Enterprise kernel security update (IMPORTANT) | 10 месяцев назад | ||
 | SUSE-SU-2024:2394-1 Security update for the Linux Kernel | 12 месяцев назад | ||
| SUSE-SU-2024:2372-1 Security update for the Linux Kernel | 12 месяцев назад | ||
| SUSE-SU-2024:2571-1 Security update for the Linux Kernel | 11 месяцев назад | ||
| SUSE-SU-2024:2896-1 Security update for the Linux Kernel | 10 месяцев назад | ||
| SUSE-SU-2024:2939-1 Security update for the Linux Kernel | 10 месяцев назад | ||
| SUSE-SU-2024:2973-1 Security update for the Linux Kernel | 10 месяцев назад |
Уязвимостей на страницу