https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 05 Nov 2026 19:22:10 +0000 https://db.gcve.eu/vuln/cve-2026-99259 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>soc/tegra: pmc: Fix uninitialised clock rate</p> <p>For legacy 32-bit Tegra devices, the warning in the tegra_pmc_enter_suspend_mode() function is being triggered because the early_pmc-&gt;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 &#39;rate&#39; to be set in the new dynamic context, but missed updating the rate in the early PMC context.</p> <p>Fix this by initialising the early_pmc-&gt;rate variable for 32-bit Tegra devices when the rate for the PMC context is initialised.</p> <p>[treding@nvidia.com: move assignment to existing #ifdef block]</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>soc/tegra: pmc: Fix uninitialised clock rate</p> <p>For legacy 32-bit Tegra devices, the warning in the tegra_pmc_enter_suspend_mode() function is being triggered because the early_pmc-&gt;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 &#39;rate&#39; to be set in the new dynamic context, but missed updating the rate in the early PMC context.</p> <p>Fix this by initialising the early_pmc-&gt;rate variable for 32-bit Tegra devices when the rate for the PMC context is initialised.</p> <p>[treding@nvidia.com: move assignment to existing #ifdef block]</p> https://db.gcve.eu/vuln/cve-2026-99259