CVE-2024-38634: serial: max3100: Lock port->lock when calling uart_handle_cts_change()
In the Linux kernel, the following vulnerability has been resolved:
serial: max3100: Lock port->lock when calling uarthandlectschange()
uarthandlectschange() 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/serialcore.c:3491 uarthandlectschange+0xa6/0xb0 ... Workqueue: max3100-0 max3100work [max3100] RIP: 0010:uarthandlectschange+0xa6/0xb0 ... max3100handlerx+0xc5/0x110 [max3100] max3100work+0x12a/0x340 [max3100]
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-38634?
The severity of CVE-2024-38634 is not specifically rated but it affects the Linux kernel, which can have significant implications for system stability and security.
How do I fix CVE-2024-38634?
To fix CVE-2024-38634, ensure you update to an unaffected version of the Linux kernel, specifically to versions 5.10.223-1, 5.10.226-1, 6.1.123-1, 6.1.119-1, 6.12.10-1, or 6.12.11-1.
What causes the vulnerability CVE-2024-38634?
CVE-2024-38634 is caused by the lack of proper locking when calling the uart_handle_cts_change() function, which can lead to race conditions.
Which systems are affected by CVE-2024-38634?
Systems running specific versions of the Linux kernel are affected by CVE-2024-38634, particularly those using the max3100 serial driver.
Is there a known exploit for CVE-2024-38634?
As of now, there are no publicly known exploits specifically targeting CVE-2024-38634 reported.