<?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>Sat, 07 Nov 2026 03:19:24 +0000</lastBuildDate>
    <item>
      <title>certfr-2026-avi-1470 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://db.gcve.eu/vuln/certfr-2026-avi-1470</link>
      <description>certfr-2026-avi-1470</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/certfr-2026-avi-1470</guid>
    </item>
    <item>
      <title>fkie_cve-2026-99089</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99089</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ASoC: samsung: i2s: enable op_clk in probe to balance runtime PM&lt;/p&gt;
&lt;p&gt;The probe function puts the device into the runtime PM active state with
only the &amp;#34;iis&amp;#34; bus clock enabled, but it also sets priv-&amp;gt;op_clk to the
parent of the RCLK_SRC mux without enabling it. The runtime PM suspend
callback disables both clocks, so the first runtime suspend after probe
disables op_clk once more than it was enabled.&lt;/p&gt;
&lt;p&gt;On Exynos5250 Arndale both clocks resolve to the same EXYNOS_I2S_BUS gate,
so this triggers the following warning during boot:&lt;/p&gt;
&lt;p&gt;WARNING: drivers/clk/clk.c:1270 at clk_core_disable+0xe4/0x23c, CPU#0: kworker/u8:3/45
 i2s_bus already disabled
 ...
 Workqueue: pm pm_runtime_work
 Call trace:
  ...
  clk_core_disable from clk_disable+0x28/0x34
  clk_disable from i2s_runtime_suspend+0x58/0x68 [snd_soc_i2s]
  i2s_runtime_suspend [snd_soc_i2s] from genpd_runtime_suspend+0xc4/0x298
  genpd_runtime_suspend from __rpm_callback+0x48/0x18c
  __rpm_callback from rpm_callback+0x4c/0x50
  rpm_callback from rpm_suspend+0xf4/0x718
  rpm_suspend from pm_runtime_work+0x9c/0xa0
  ...&lt;/p&gt;
&lt;p&gt;Fix this by enabling op_clk in probe right after getting it, so the clock
state matches the runtime PM active state, and by disabling it in remove.&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;ASoC: samsung: i2s: enable op_clk in probe to balance runtime PM&lt;/p&gt;
&lt;p&gt;The probe function puts the device into the runtime PM active state with
only the &amp;#34;iis&amp;#34; bus clock enabled, but it also sets priv-&amp;gt;op_clk to the
parent of the RCLK_SRC mux without enabling it. The runtime PM suspend
callback disables both clocks, so the first runtime suspend after probe
disables op_clk once more than it was enabled.&lt;/p&gt;
&lt;p&gt;On Exynos5250 Arndale both clocks resolve to the same EXYNOS_I2S_BUS gate,
so this triggers the following warning during boot:&lt;/p&gt;
&lt;p&gt;WARNING: drivers/clk/clk.c:1270 at clk_core_disable+0xe4/0x23c, CPU#0: kworker/u8:3/45
 i2s_bus already disabled
 ...
 Workqueue: pm pm_runtime_work
 Call trace:
  ...
  clk_core_disable from clk_disable+0x28/0x34
  clk_disable from i2s_runtime_suspend+0x58/0x68 [snd_soc_i2s]
  i2s_runtime_suspend [snd_soc_i2s] from genpd_runtime_suspend+0xc4/0x298
  genpd_runtime_suspend from __rpm_callback+0x48/0x18c
  __rpm_callback from rpm_callback+0x4c/0x50
  rpm_callback from rpm_suspend+0xf4/0x718
  rpm_suspend from pm_runtime_work+0x9c/0xa0
  ...&lt;/p&gt;
&lt;p&gt;Fix this by enabling op_clk in probe right after getting it, so the clock
state matches the runtime PM active state, and by disabling it in remove.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99089</guid>
    </item>
    <item>
      <title>GHSA-xc7f-3c97-gfm9</title>
      <link>https://db.gcve.eu/vuln/ghsa-xc7f-3c97-gfm9</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ASoC: samsung: i2s: enable op_clk in probe to balance runtime PM&lt;/p&gt;
&lt;p&gt;The probe function puts the device into the runtime PM active state with
only the &amp;#34;iis&amp;#34; bus clock enabled, but it also sets priv-&amp;gt;op_clk to the
parent of the RCLK_SRC mux without enabling it. The runtime PM suspend
callback disables both clocks, so the first runtime suspend after probe
disables op_clk once more than it was enabled.&lt;/p&gt;
&lt;p&gt;On Exynos5250 Arndale both clocks resolve to the same EXYNOS_I2S_BUS gate,
so this triggers the following warning during boot:&lt;/p&gt;
&lt;p&gt;WARNING: drivers/clk/clk.c:1270 at clk_core_disable+0xe4/0x23c, CPU#0: kworker/u8:3/45
 i2s_bus already disabled
 ...
 Workqueue: pm pm_runtime_work
 Call trace:
  ...
  clk_core_disable from clk_disable+0x28/0x34
  clk_disable from i2s_runtime_suspend+0x58/0x68 [snd_soc_i2s]
  i2s_runtime_suspend [snd_soc_i2s] from genpd_runtime_suspend+0xc4/0x298
  genpd_runtime_suspend from __rpm_callback+0x48/0x18c
  __rpm_callback from rpm_callback+0x4c/0x50
  rpm_callback from rpm_suspend+0xf4/0x718
  rpm_suspend from pm_runtime_work+0x9c/0xa0
  ...&lt;/p&gt;
&lt;p&gt;Fix this by enabling op_clk in probe right after getting it, so the clock
state matches the runtime PM active state, and by disabling it in remove.&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;ASoC: samsung: i2s: enable op_clk in probe to balance runtime PM&lt;/p&gt;
&lt;p&gt;The probe function puts the device into the runtime PM active state with
only the &amp;#34;iis&amp;#34; bus clock enabled, but it also sets priv-&amp;gt;op_clk to the
parent of the RCLK_SRC mux without enabling it. The runtime PM suspend
callback disables both clocks, so the first runtime suspend after probe
disables op_clk once more than it was enabled.&lt;/p&gt;
&lt;p&gt;On Exynos5250 Arndale both clocks resolve to the same EXYNOS_I2S_BUS gate,
so this triggers the following warning during boot:&lt;/p&gt;
&lt;p&gt;WARNING: drivers/clk/clk.c:1270 at clk_core_disable+0xe4/0x23c, CPU#0: kworker/u8:3/45
 i2s_bus already disabled
 ...
 Workqueue: pm pm_runtime_work
 Call trace:
  ...
  clk_core_disable from clk_disable+0x28/0x34
  clk_disable from i2s_runtime_suspend+0x58/0x68 [snd_soc_i2s]
  i2s_runtime_suspend [snd_soc_i2s] from genpd_runtime_suspend+0xc4/0x298
  genpd_runtime_suspend from __rpm_callback+0x48/0x18c
  __rpm_callback from rpm_callback+0x4c/0x50
  rpm_callback from rpm_suspend+0xf4/0x718
  rpm_suspend from pm_runtime_work+0x9c/0xa0
  ...&lt;/p&gt;
&lt;p&gt;Fix this by enabling op_clk in probe right after getting it, so the clock
state matches the runtime PM active state, and by disabling it in remove.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-xc7f-3c97-gfm9</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-99089 — ASoC: samsung: i2s: enable op_clk in probe to balance runtime PM</title>
      <link>https://db.gcve.eu/vuln/msrc_cve-2026-99089</link>
      <description>msrc_CVE-2026-99089</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/msrc_cve-2026-99089</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:24550-1 — Security update for the Linux Kernel</title>
      <link>https://db.gcve.eu/vuln/suse-su-2026:24550-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/suse-su-2026:24550-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-99089</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2026-99089</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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 229 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ASoC: samsung: i2s: enable op_clk in probe to balance runtime PM The probe function puts the device into the runtime PM active state with only the &amp;#34;iis&amp;#34; bus clock enabled, but it also sets priv-&amp;gt;op_clk to the parent of the RCLK_SRC mux without enabling it. The runtime PM suspend callback disables both clocks, so the first runtime suspend after probe disables op_clk once more than it was enabled. On Exynos5250 Arndale both clocks resolve to the same EXYNOS_I2S_BUS gate, so this triggers the following warning during boot:  WARNING: drivers/clk/clk.c:1270 at clk_core_disable+0xe4/0x23c, CPU#0: kworker/u8:3/45  i2s_bus already disabled  ...  Workqueue: pm pm_runtime_work  Call trace:   ...   clk_core_disable from clk_disable+0x28/0x34   clk_disable from i2s_runtime_suspend+0x58/0x68 [snd_soc_i2s]   i2s_runtime_suspend [snd_soc_i2s] from genpd_runtime_suspend+0xc4/0x298   genpd_runtime_suspend from __rpm_callback+0x48/0x18c   __rpm_callback from rpm_callback+0x4c/0x50   rpm_callback from rpm_suspend+0xf4/0x718   rpm_suspend from pm_runtime_work+0x9c/0xa0   ... Fix this by enabling op_clk in probe right after getting it, so the clock state matches the runtime PM active state, and by disabling it in remove.&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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 229 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ASoC: samsung: i2s: enable op_clk in probe to balance runtime PM The probe function puts the device into the runtime PM active state with only the &amp;#34;iis&amp;#34; bus clock enabled, but it also sets priv-&amp;gt;op_clk to the parent of the RCLK_SRC mux without enabling it. The runtime PM suspend callback disables both clocks, so the first runtime suspend after probe disables op_clk once more than it was enabled. On Exynos5250 Arndale both clocks resolve to the same EXYNOS_I2S_BUS gate, so this triggers the following warning during boot:  WARNING: drivers/clk/clk.c:1270 at clk_core_disable+0xe4/0x23c, CPU#0: kworker/u8:3/45  i2s_bus already disabled  ...  Workqueue: pm pm_runtime_work  Call trace:   ...   clk_core_disable from clk_disable+0x28/0x34   clk_disable from i2s_runtime_suspend+0x58/0x68 [snd_soc_i2s]   i2s_runtime_suspend [snd_soc_i2s] from genpd_runtime_suspend+0xc4/0x298   genpd_runtime_suspend from __rpm_callback+0x48/0x18c   __rpm_callback from rpm_callback+0x4c/0x50   rpm_callback from rpm_suspend+0xf4/0x718   rpm_suspend from pm_runtime_work+0x9c/0xa0   ... Fix this by enabling op_clk in probe right after getting it, so the clock state matches the runtime PM active state, and by disabling it in remove.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2026-99089</guid>
    </item>
  </channel>
</rss>
