can: mcp251x: fix resume from sleep before interface was brought up
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
can: mcp251x: fix resume from sleep before interface was brought up
Since 8ce8c0abcba3 the driver queues work via priv->restart_work when resuming after suspend, even when the interface was not previously enabled. This causes a null dereference error as the workqueue is only allocated and initialized in mcp251x_open().
To fix this we move the workqueue init to mcp251x_can_probe() as there is no reason to do it later and repeat it whenever mcp251x_open() is called.
[mkl: fix error handling in mcp251x_stop()]
From the CVE record · Linux
The Linux kernel’s mcp251x CAN driver can queue work on an uninitialized workqueue when resuming from sleep before the interface has been brought up, causing a null-pointer dereference. The input does not specify whether an attacker can trigger this condition or what access or user interaction would be required.
Operators running Linux kernels with the mcp251x CAN driver should check their installations; affected versions are not specified.