<?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>Tue, 03 Nov 2026 07:22:47 +0000</lastBuildDate>
    <item>
      <title>certfr-2026-avi-1375 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
      <link>https://db.gcve.eu/vuln/certfr-2026-avi-1375</link>
      <description>certfr-2026-avi-1375</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/certfr-2026-avi-1375</guid>
    </item>
    <item>
      <title>fkie_cve-2026-98825</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-98825</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;rtc: mpfs: fix unchecked devm_clk_get() error pointer in probe()&lt;/p&gt;
&lt;p&gt;devm_clk_get(&amp;amp;pdev-&amp;gt;dev, &amp;#34;rtcref&amp;#34;)&amp;#39;s return value was passed straight
into clk_get_rate() without checking it for an error first, unlike the
&amp;#34;rtc&amp;#34; clock a few lines above which is correctly checked with
IS_ERR(). clk_get_rate() only guards against a NULL clk, not an error
pointer:&lt;/p&gt;
&lt;p&gt;if (!clk)
		return 0;
	...
	rate = clk_core_get_rate_recalc(clk-&amp;gt;core);&lt;/p&gt;
&lt;p&gt;so if devm_clk_get() ever returns an error pointer here (for example
ERR_PTR(-EPROBE_DEFER), which is the normal, expected outcome if the
clkcfg clock-provider this RTC depends on has not registered its
clocks yet by the time this driver probes), clk_get_rate() dereferences
that error pointer instead of returning 0, crashing instead of letting
probe defer.&lt;/p&gt;
&lt;p&gt;Capture the clock in the existing &amp;#39;clk&amp;#39; local and check it with
IS_ERR() before calling clk_get_rate(), matching the handling already
used for the &amp;#34;rtc&amp;#34; clock in this same function.&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;rtc: mpfs: fix unchecked devm_clk_get() error pointer in probe()&lt;/p&gt;
&lt;p&gt;devm_clk_get(&amp;amp;pdev-&amp;gt;dev, &amp;#34;rtcref&amp;#34;)&amp;#39;s return value was passed straight
into clk_get_rate() without checking it for an error first, unlike the
&amp;#34;rtc&amp;#34; clock a few lines above which is correctly checked with
IS_ERR(). clk_get_rate() only guards against a NULL clk, not an error
pointer:&lt;/p&gt;
&lt;p&gt;if (!clk)
		return 0;
	...
	rate = clk_core_get_rate_recalc(clk-&amp;gt;core);&lt;/p&gt;
&lt;p&gt;so if devm_clk_get() ever returns an error pointer here (for example
ERR_PTR(-EPROBE_DEFER), which is the normal, expected outcome if the
clkcfg clock-provider this RTC depends on has not registered its
clocks yet by the time this driver probes), clk_get_rate() dereferences
that error pointer instead of returning 0, crashing instead of letting
probe defer.&lt;/p&gt;
&lt;p&gt;Capture the clock in the existing &amp;#39;clk&amp;#39; local and check it with
IS_ERR() before calling clk_get_rate(), matching the handling already
used for the &amp;#34;rtc&amp;#34; clock in this same function.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-98825</guid>
    </item>
    <item>
      <title>GHSA-44qj-hfjm-pr88</title>
      <link>https://db.gcve.eu/vuln/ghsa-44qj-hfjm-pr88</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;rtc: mpfs: fix unchecked devm_clk_get() error pointer in probe()&lt;/p&gt;
&lt;p&gt;devm_clk_get(&amp;amp;pdev-&amp;gt;dev, &amp;#34;rtcref&amp;#34;)&amp;#39;s return value was passed straight
into clk_get_rate() without checking it for an error first, unlike the
&amp;#34;rtc&amp;#34; clock a few lines above which is correctly checked with
IS_ERR(). clk_get_rate() only guards against a NULL clk, not an error
pointer:&lt;/p&gt;
&lt;p&gt;if (!clk)
		return 0;
	...
	rate = clk_core_get_rate_recalc(clk-&amp;gt;core);&lt;/p&gt;
&lt;p&gt;so if devm_clk_get() ever returns an error pointer here (for example
ERR_PTR(-EPROBE_DEFER), which is the normal, expected outcome if the
clkcfg clock-provider this RTC depends on has not registered its
clocks yet by the time this driver probes), clk_get_rate() dereferences
that error pointer instead of returning 0, crashing instead of letting
probe defer.&lt;/p&gt;
&lt;p&gt;Capture the clock in the existing &amp;#39;clk&amp;#39; local and check it with
IS_ERR() before calling clk_get_rate(), matching the handling already
used for the &amp;#34;rtc&amp;#34; clock in this same function.&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;rtc: mpfs: fix unchecked devm_clk_get() error pointer in probe()&lt;/p&gt;
&lt;p&gt;devm_clk_get(&amp;amp;pdev-&amp;gt;dev, &amp;#34;rtcref&amp;#34;)&amp;#39;s return value was passed straight
into clk_get_rate() without checking it for an error first, unlike the
&amp;#34;rtc&amp;#34; clock a few lines above which is correctly checked with
IS_ERR(). clk_get_rate() only guards against a NULL clk, not an error
pointer:&lt;/p&gt;
&lt;p&gt;if (!clk)
		return 0;
	...
	rate = clk_core_get_rate_recalc(clk-&amp;gt;core);&lt;/p&gt;
&lt;p&gt;so if devm_clk_get() ever returns an error pointer here (for example
ERR_PTR(-EPROBE_DEFER), which is the normal, expected outcome if the
clkcfg clock-provider this RTC depends on has not registered its
clocks yet by the time this driver probes), clk_get_rate() dereferences
that error pointer instead of returning 0, crashing instead of letting
probe defer.&lt;/p&gt;
&lt;p&gt;Capture the clock in the existing &amp;#39;clk&amp;#39; local and check it with
IS_ERR() before calling clk_get_rate(), matching the handling already
used for the &amp;#34;rtc&amp;#34; clock in this same function.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-44qj-hfjm-pr88</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-98825 — rtc: mpfs: fix unchecked devm_clk_get() error pointer in probe()</title>
      <link>https://db.gcve.eu/vuln/msrc_cve-2026-98825</link>
      <description>msrc_CVE-2026-98825</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/msrc_cve-2026-98825</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98825</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2026-98825</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 154 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: rtc: mpfs: fix unchecked devm_clk_get() error pointer in probe() devm_clk_get(&amp;amp;pdev-&amp;gt;dev, &amp;#34;rtcref&amp;#34;)&amp;#39;s return value was passed straight into clk_get_rate() without checking it for an error first, unlike the &amp;#34;rtc&amp;#34; clock a few lines above which is correctly checked with IS_ERR(). clk_get_rate() only guards against a NULL clk, not an error pointer: 	if (!clk) 		return 0; 	... 	rate = clk_core_get_rate_recalc(clk-&amp;gt;core); so if devm_clk_get() ever returns an error pointer here (for example ERR_PTR(-EPROBE_DEFER), which is the normal, expected outcome if the clkcfg clock-provider this RTC depends on has not registered its clocks yet by the time this driver probes), clk_get_rate() dereferences that error pointer instead of returning 0, crashing instead of letting probe defer. Capture the clock in the existing &amp;#39;clk&amp;#39; local and check it with IS_ERR() before calling clk_get_rate(), matching the handling already used for the &amp;#34;rtc&amp;#34; clock in this same function.&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 154 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: rtc: mpfs: fix unchecked devm_clk_get() error pointer in probe() devm_clk_get(&amp;amp;pdev-&amp;gt;dev, &amp;#34;rtcref&amp;#34;)&amp;#39;s return value was passed straight into clk_get_rate() without checking it for an error first, unlike the &amp;#34;rtc&amp;#34; clock a few lines above which is correctly checked with IS_ERR(). clk_get_rate() only guards against a NULL clk, not an error pointer: 	if (!clk) 		return 0; 	... 	rate = clk_core_get_rate_recalc(clk-&amp;gt;core); so if devm_clk_get() ever returns an error pointer here (for example ERR_PTR(-EPROBE_DEFER), which is the normal, expected outcome if the clkcfg clock-provider this RTC depends on has not registered its clocks yet by the time this driver probes), clk_get_rate() dereferences that error pointer instead of returning 0, crashing instead of letting probe defer. Capture the clock in the existing &amp;#39;clk&amp;#39; local and check it with IS_ERR() before calling clk_get_rate(), matching the handling already used for the &amp;#34;rtc&amp;#34; clock in this same function.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2026-98825</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4019 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4019</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2026-4019</guid>
    </item>
  </channel>
</rss>
