<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 05 Nov 2026 07:11:35 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99259</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99259</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;soc/tegra: pmc: Fix uninitialised clock rate&lt;/p&gt;
&lt;p&gt;For legacy 32-bit Tegra devices, the warning in the
tegra_pmc_enter_suspend_mode() function is being triggered because the
early_pmc-&amp;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 &amp;#39;rate&amp;#39; to be set in the new dynamic
context, but missed updating the rate in the early PMC context.&lt;/p&gt;
&lt;p&gt;Fix this by initialising the early_pmc-&amp;gt;rate variable for 32-bit Tegra
devices when the rate for the PMC context is initialised.&lt;/p&gt;
&lt;p&gt;[treding@nvidia.com: move assignment to existing #ifdef block]&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;soc/tegra: pmc: Fix uninitialised clock rate&lt;/p&gt;
&lt;p&gt;For legacy 32-bit Tegra devices, the warning in the
tegra_pmc_enter_suspend_mode() function is being triggered because the
early_pmc-&amp;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 &amp;#39;rate&amp;#39; to be set in the new dynamic
context, but missed updating the rate in the early PMC context.&lt;/p&gt;
&lt;p&gt;Fix this by initialising the early_pmc-&amp;gt;rate variable for 32-bit Tegra
devices when the rate for the PMC context is initialised.&lt;/p&gt;
&lt;p&gt;[treding@nvidia.com: move assignment to existing #ifdef block]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99259</guid>
    </item>
    <item>
      <title>GHSA-mrwj-wrmj-995m</title>
      <link>https://db.gcve.eu/vuln/ghsa-mrwj-wrmj-995m</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;soc/tegra: pmc: Fix uninitialised clock rate&lt;/p&gt;
&lt;p&gt;For legacy 32-bit Tegra devices, the warning in the
tegra_pmc_enter_suspend_mode() function is being triggered because the
early_pmc-&amp;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 &amp;#39;rate&amp;#39; to be set in the new dynamic
context, but missed updating the rate in the early PMC context.&lt;/p&gt;
&lt;p&gt;Fix this by initialising the early_pmc-&amp;gt;rate variable for 32-bit Tegra
devices when the rate for the PMC context is initialised.&lt;/p&gt;
&lt;p&gt;[treding@nvidia.com: move assignment to existing #ifdef block]&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;soc/tegra: pmc: Fix uninitialised clock rate&lt;/p&gt;
&lt;p&gt;For legacy 32-bit Tegra devices, the warning in the
tegra_pmc_enter_suspend_mode() function is being triggered because the
early_pmc-&amp;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 &amp;#39;rate&amp;#39; to be set in the new dynamic
context, but missed updating the rate in the early PMC context.&lt;/p&gt;
&lt;p&gt;Fix this by initialising the early_pmc-&amp;gt;rate variable for 32-bit Tegra
devices when the rate for the PMC context is initialised.&lt;/p&gt;
&lt;p&gt;[treding@nvidia.com: move assignment to existing #ifdef block]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-mrwj-wrmj-995m</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-99259</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2026-99259</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 105 more&lt;/p&gt;
&lt;p&gt;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-&amp;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 &amp;#39;rate&amp;#39; 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-&amp;gt;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]&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 105 more&lt;/p&gt;
&lt;p&gt;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-&amp;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 &amp;#39;rate&amp;#39; 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-&amp;gt;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]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2026-99259</guid>
    </item>
  </channel>
</rss>
