um: Add winch to winch_handlers before registering winch IRQ
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 42a359e31a0e438b5b978a8f0fecdbd3c86bb033 · < 434a06c38ee1217a8baa0dd7c37cc85d50138fb0| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
um: Add winch to winch_handlers before registering winch IRQ
Registering a winch IRQ is racy, an interrupt may occur before the winch is added to the winch_handlers list.
If that happens, register_winch_irq() adds to that list a winch that is scheduled to be (or has already been) freed, causing a panic later in winch_cleanup().
Avoid the race by adding the winch to the winch_handlers list before registering the IRQ, and rolling back if um_request_irq() fails.
From the CVE record · Linux
The Linux kernel has a race when registering a winch IRQ: an interrupt can occur before the winch is added to the handler list. This can leave a freed or soon-to-be-freed entry on the list and cause a later kernel panic during cleanup. The input does not specify how an attacker could trigger the race or whether authentication or user interaction is required.
Engineers running Linux kernels with UML winch IRQ handling should check their kernel; affected versions are not specified.