firmware: arm_scpi: Ensure scpi_info is not assigned if the probe fails
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 8cb7cf56c9fe5412de238465b27ef35b4d2801aa · < 4f2d7b46d6b53c07f44a4f8f8f4438888f0e9e87| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
firmware: arm_scpi: Ensure scpi_info is not assigned if the probe fails
When scpi probe fails, at any point, we need to ensure that the scpi_info is not set and will remain NULL until the probe succeeds. If it is not taken care, then it could result use-after-free as the value is exported via get_scpi_ops() and could refer to a memory allocated via devm_kzalloc() but freed when the probe fails.
From the CVE record · Linux
If the arm_scpi probe fails, scpi_info can remain set to memory that has been freed. A subsequent call to get_scpi_ops() could access that freed memory. The input does not specify an attacker path, authentication requirement, or user interaction.
Engineers running the Linux kernel with the arm_scpi firmware driver should check their systems; affected versions are not specified.