spi: tegra20-slink: fix UAF in tegra_slink_remove()
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:
spi: tegra20-slink: fix UAF in tegra_slink_remove()
After calling spi_unregister_master(), the refcount of master will be decrease to 0, and it will be freed in spi_controller_release(), the device data also will be freed, so it will lead a UAF when using 'tspi'. To fix this, get the master before unregister and put it when finish using it.
From the CVE record · Linux
The Linux kernel's tegra20-slink driver can use freed device data during tegra_slink_remove() after spi_unregister_master() releases the controller. The input does not specify how an attacker could trigger this condition or whether access or user interaction is required.
Engineers running Linux kernels with the tegra20-slink driver should check their exposure; affected versions are not specified.