soc: aspeed: Add NULL check in aspeed_lpc_enable_snoop()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 3772e5da445420543b25825ac2b5971f3743f6e8 · < f697ef117ecbf3a367dfc559a6a3589905956530| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
soc: aspeed: Add NULL check in aspeed_lpc_enable_snoop()
devm_kasprintf() returns NULL when memory allocation fails. Currently, aspeed_lpc_enable_snoop() does not check for this case, which results in a NULL pointer dereference.
Add NULL check after devm_kasprintf() to prevent this issue.
[arj: Fix Fixes: tag to use subject from 3772e5da4454]
From the CVE record · Linux
The Linux kernel's aspeed_lpc_enable_snoop() can dereference a NULL pointer if devm_kasprintf() fails to allocate memory. This could cause a crash; the input does not specify how an attacker could trigger the failure or whether access or user interaction is required.
Engineers running Linux kernels with the Aspeed LPC snoop component should check their deployments; affected versions are not specified.