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]
History

No history.

cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published: 2024-06-21T10:18:23.573Z

Updated: 2024-11-05T09:31:21.961Z

Reserved: 2024-06-18T19:36:34.947Z

Link: CVE-2024-38634

cve-icon Vulnrichment

Updated: 2024-06-21T13:19:15.886Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2024-06-21T11:15:12.160

Modified: 2024-07-15T07:15:13.910

Link: CVE-2024-38634

cve-icon Redhat

Severity : Low

Publid Date: 2024-06-21T00:00:00Z

Links: CVE-2024-38634 - Bugzilla