x86/boot: Validate console=uart8250 baud rate to fix early boot hang
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ce0aa5dd20e44372f9617dd67c984f41fcdbed88 · < f7c67c97b37c11f2a95c204092fb8159f2779e8f| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
x86/boot: Validate console=uart8250 baud rate to fix early boot hang
When the baud rate is empty, 0, invalid, or overflows to 0 when stored as an int, the system will hang during early boot because of a division by zero in early_serial_init().
Fall back to DEFAULT_BAUD when the resulting baud rate is 0 to prevent an early system hang.
From the CVE record · Linux
The Linux kernel can hang during early boot if the console=uart8250 baud rate is empty, zero, invalid, or overflows to zero. This causes a division by zero in early_serial_init(). The input does not establish an attacker path, authentication requirement, or user-interaction requirement.
Engineers running Linux kernels that use the x86 early serial console should check their systems; affected versions were not provided.