Linux kernel suspend warning in Tegra PMC clock setup
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:
soc/tegra: pmc: Fix uninitialised clock rate
For legacy 32-bit Tegra devices, the warning in the tegra_pmc_enter_suspend_mode() function is being triggered because the early_pmc->rate variable is never configured and hence, always 0. This issue started occurring after updating the PMC driver to create the PMC context dynamically which causes the 'rate' to be set in the new dynamic context, but missed updating the rate in the early PMC context.
Fix this by initialising the early_pmc->rate variable for 32-bit Tegra devices when the rate for the PMC context is initialised.
[treding@nvidia.com: move assignment to existing #ifdef block]
From the CVE record · Linux
On legacy 32-bit Tegra devices, the Linux kernel’s PMC driver leaves the early PMC clock rate uninitialized, triggering a warning when entering suspend mode. The input describes no attacker action or exploit conditions; network access, authentication requirements, and user interaction are not specified.
Engineers running the Linux kernel on legacy 32-bit Tegra devices should check their kernel version; affected versions are not specified.