serial: 8250: fix possible ISR soft lockup
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · < 4295c58990b7a84e8349a2226db692e252825b60| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
serial: 8250: fix possible ISR soft lockup
There are rare cases in which the host gets stuck in the ISR because it is flooded with messages during the startup phase.
The reason for the soft lockup in the ISR is the missing FIFO error IRQ (FIFOE) handling. Not handling it and reporting IRQ_HANDLED triggers the IRQ immediately again.
Fix this by adding a check for the FIFOE status and clearing the FIFO if no data is ready (DR).
This behavior was observed on an AM62L device which uses the OMAP 8250 driver. Fix it for all 8250 drivers, since the OMAP driver's special IRQ setup handling may trigger this behavior more frequently, but it is not ensured that other 8250 drivers aren't affected.
From the CVE record · Linux
The Linux kernel’s 8250 serial interrupt handler can enter a soft lockup when flooded with messages during startup because it does not handle a FIFO error interrupt. This was observed on an AM62L device using the OMAP 8250 driver; other 8250 drivers may also be affected. The input does not establish an attacker path, authentication requirement, or user interaction requirement.
Engineers running Linux kernels with 8250 serial drivers should check their installations; affected versions were not specified.