serial: 8250: Fix oops for port->pm on uart_change_pm()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ af4d6dbb1a92ea424ad1ba1d0c88c7fa2345d872 · < 0c05493341d6f2097f75f0a5dbb7b53a9e8c5f6c| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
serial: 8250: Fix oops for port->pm on uart_change_pm()
Unloading a hardware specific 8250 driver can produce error "Unable to handle kernel paging request at virtual address" about ten seconds after unloading the driver. This happens on uart_hangup() calling uart_change_pm().
Turns out commit 04e82793f068 ("serial: 8250: Reinit port->pm on port specific driver unbind") was only a partial fix. If the hardware specific driver has initialized port->pm function, we need to clear port->pm too. Just reinitializing port->ops does not do this. Otherwise serial8250_pm() will call port->pm() instead of serial8250_do_pm().
From the CVE record · Linux
The Linux kernel’s 8250 serial driver can hit a kernel paging error when a hardware-specific driver is unloaded. The error can occur about ten seconds later during serial port hangup if the driver’s power-management function was not cleared. The input does not describe an attacker, authentication requirements, or user interaction.
Engineers running Linux kernels with hardware-specific 8250 serial drivers should check their kernel versions; affected versions are not specified.