mmc: sdhci-of-aspeed: Remove children before releasing SDC resources
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ bb7b8ec62dfb9b255027c3a54d01f12fc3bd1d2c · < 15b5ffd8af2dd46856da57467eb6e0f90d8ada51| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
mmc: sdhci-of-aspeed: Remove children before releasing SDC resources
Probe failure and removal leave SDHCI child devices registered after the parent clock and managed resources are released.
Unregister the OF children in reverse order before disabling the parent clock on both paths. Use of_platform_device_destroy() because manual child creation does not set the flag required by of_platform_depopulate().
This issue was identified during our ongoing static-analysis research while reviewing kernel code.
From the CVE record · Linux
The Linux kernel's sdhci-of-aspeed driver can leave SDHCI child devices registered after parent resources are released during probe failure or removal. The input does not establish what an attacker could do or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with the sdhci-of-aspeed driver should check whether their kernel includes the fix; affected versions are not specified.