serial: max3100: Update uart_driver_registered on driver removal
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 7831d56b0a3544cbb6f82f76c34ca95e24d5b676 · < e8a10089eddba40d4b2080c9d3fc2d2b2488f762| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
serial: max3100: Update uart_driver_registered 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: max3100_probe: adding port 0 BUG: kernel NULL pointer dereference, address: 0000000000000408 ... RIP: 0010:serial_core_register_port+0xa0/0x840 ... max3100_probe+0x1b6/0x280 [max3100] spi_probe+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 uart_register_driver() call.
From the CVE record · Linux
The Linux kernel MAX3100 serial driver can leave its registration state incorrect when the last MAX3100 device is removed. A subsequent load–unload–load cycle can cause a kernel NULL pointer dereference and oops. The input does not establish whether an attacker can trigger this remotely or what access is required.
Engineers running Linux kernels with the MAX3100 serial driver should check their exposure; affected versions were not provided.