UBUNTU-CVE-2026-99259: Medium severity ubuntu/linux vulnerability
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 tegrapmcentersuspendmode() function is being triggered because the earlypmc->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 earlypmc->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]
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
For legacy 32-bit Tegra devices, initialize early_pmc->rate when the PMC context rate is initialized, within the existing conditional compilation block.
Linux kernel soc/tegra PMC driver early_pmc->rate = initialized to the PMC context rate
Event History
Frequently Asked Questions
Which systems are affected by this issue?
The issue applies to legacy 32-bit Tegra devices using the Linux kernel packages listed for Ubuntu. The affected code path is associated with suspend handling in the Tegra PMC driver.
What behavior indicates that a system may be affected?
Affected systems can trigger a warning in tegra_pmc_enter_suspend_mode() because the early PMC clock-rate value is left at zero. This is most relevant when the system enters suspend mode.
Is there an immediate workaround if an updated kernel is unavailable?
The provided information does not identify a workaround. Since the warning is triggered during suspend handling, avoiding suspend may avoid exercising the affected path, but this is not stated as a supported mitigation.