Live › vulnerability › CVE-2026-99259
On legacy 32-bit NVIDIA Tegra devices, the Linux kernel's power management controller driver never sets a clock rate variable, so a warning fires during suspend. The description does not state any attacker-usable effect beyond this warning.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-03 12:20 UTC. All times on this page are UTC.
Affects Linux kernels running on legacy 32-bit Tegra hardware whose power management controller driver was changed to allocate its context dynamically. Systems on other architectures or without 32-bit Tegra boards are not described as affected. unknown whether the sources name a fixed kernel version.
No product ranges from the sources yet.
Unknown from the sources.
Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
[[email protected]: move assignment to existing #ifdef block]
This page as .md · .json · in your agent: get_signal("CVE-2026-99259")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.