CVE-2024-38633: serial: max3100: Update uart_driver_registered on driver removal
In the Linux kernel, the following vulnerability has been resolved:
serial: max3100: Update uartdriverregistered on driver removal
The removal of the last MAX3100 device triggers the removal of the driver. However, code doesn't update the respective global variable and after insmod — rmmod — insmod cycle the kernel oopses:
max3100 spi-PRP0001:01: max3100probe: adding port 0 BUG: kernel NULL pointer dereference, address: 0000000000000408 ... RIP: 0010:serialcoreregisterport+0xa0/0x840 ... max3100probe+0x1b6/0x280 [max3100] spiprobe+0x8d/0xb0
Update the actual state so next time UART driver will be registered again.
Hugo also noticed, that the error path in the probe also affected by having the variable set, and not cleared. Instead of clearing it move the assignment after the successfull uartregisterdriver() call.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-38633?
CVE-2024-38633 has been classified with a critical severity level due to its impact on system stability.
How do I fix CVE-2024-38633?
To fix CVE-2024-38633, update your Linux kernel to the latest patched version such as 5.10.223-1 or 6.12.12-1.
Which versions of the Linux kernel are affected by CVE-2024-38633?
CVE-2024-38633 affects Linux kernel versions from 2.6.30 up to 6.6.33.
What systems are vulnerable to CVE-2024-38633?
Systems running affected versions of the Linux kernel with the MAX3100 driver are vulnerable to CVE-2024-38633.
Is there a patch available for CVE-2024-38633?
Yes, patches are available in the newer kernel releases to address CVE-2024-38633.