<?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://cve.radiocsirt.org</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>Wed, 21 Oct 2026 16:30:09 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-04036</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-04036</link>
      <description>bdu:2026-04036</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-04036</guid>
    </item>
    <item>
      <title>EUVD-2026-310522</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-310522</link>
      <description>EUVD-2026-310522</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-310522</guid>
    </item>
    <item>
      <title>fkie_cve-2022-49383</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-49383</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;watchdog: rzg2l_wdt: Fix &amp;#39;BUG: Invalid wait context&amp;#39;&lt;/p&gt;
&lt;p&gt;This patch fixes the issue &amp;#39;BUG: Invalid wait context&amp;#39; during restart()
callback by using clk_prepare_enable() instead of pm_runtime_get_sync()
for turning on the clocks during restart.&lt;/p&gt;
&lt;p&gt;This issue is noticed when testing with renesas_defconfig.&lt;/p&gt;
&lt;p&gt;[   42.213802] reboot: Restarting system
[   42.217860]
[   42.219364] =============================
[   42.223368] [ BUG: Invalid wait context ]
[   42.227372] 5.17.0-rc5-arm64-renesas-00002-g10393723e35e #522 Not tainted
[   42.234153] -----------------------------
[   42.238155] systemd-shutdow/1 is trying to lock:
[   42.242766] ffff00000a650828 (&amp;amp;genpd-&amp;gt;mlock){+.+.}-{3:3}, at: genpd_lock_mtx+0x14/0x20
[   42.250709] other info that might help us debug this:
[   42.255753] context-{4:4}
[   42.258368] 2 locks held by systemd-shutdow/1:
[   42.262806]  #0: ffff80000944e1c8 (system_transition_mutex#2){+.+.}-{3:3}, at: __do_sys_reboot+0xd0/0x250
[   42.272388]  #1: ffff8000094c4e40 (rcu_read_lock){....}-{1:2}, at: atomic_notifier_call_chain+0x0/0x150
[   42.281795] stack backtrace:
[   42.284672] CPU: 0 PID: 1 Comm: systemd-shutdow Not tainted 5.17.0-rc5-arm64-renesas-00002-g10393723e35e #522
[   42.294577] Hardware name: Renesas SMARC EVK based on r9a07g044c2 (DT)
[   42.301096] Call trace:
[   42.303538]  dump_backtrace+0xcc/0xd8
[   42.307203]  show_stack+0x14/0x30
[   42.310517]  dump_stack_lvl+0x88/0xb0
[…&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;watchdog: rzg2l_wdt: Fix &amp;#39;BUG: Invalid wait context&amp;#39;&lt;/p&gt;
&lt;p&gt;This patch fixes the issue &amp;#39;BUG: Invalid wait context&amp;#39; during restart()
callback by using clk_prepare_enable() instead of pm_runtime_get_sync()
for turning on the clocks during restart.&lt;/p&gt;
&lt;p&gt;This issue is noticed when testing with renesas_defconfig.&lt;/p&gt;
&lt;p&gt;[   42.213802] reboot: Restarting system
[   42.217860]
[   42.219364] =============================
[   42.223368] [ BUG: Invalid wait context ]
[   42.227372] 5.17.0-rc5-arm64-renesas-00002-g10393723e35e #522 Not tainted
[   42.234153] -----------------------------
[   42.238155] systemd-shutdow/1 is trying to lock:
[   42.242766] ffff00000a650828 (&amp;amp;genpd-&amp;gt;mlock){+.+.}-{3:3}, at: genpd_lock_mtx+0x14/0x20
[   42.250709] other info that might help us debug this:
[   42.255753] context-{4:4}
[   42.258368] 2 locks held by systemd-shutdow/1:
[   42.262806]  #0: ffff80000944e1c8 (system_transition_mutex#2){+.+.}-{3:3}, at: __do_sys_reboot+0xd0/0x250
[   42.272388]  #1: ffff8000094c4e40 (rcu_read_lock){....}-{1:2}, at: atomic_notifier_call_chain+0x0/0x150
[   42.281795] stack backtrace:
[   42.284672] CPU: 0 PID: 1 Comm: systemd-shutdow Not tainted 5.17.0-rc5-arm64-renesas-00002-g10393723e35e #522
[   42.294577] Hardware name: Renesas SMARC EVK based on r9a07g044c2 (DT)
[   42.301096] Call trace:
[   42.303538]  dump_backtrace+0xcc/0xd8
[   42.307203]  show_stack+0x14/0x30
[   42.310517]  dump_stack_lvl+0x88/0xb0
[…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-49383</guid>
    </item>
    <item>
      <title>GHSA-h447-c2wm-jgwc</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-h447-c2wm-jgwc</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;watchdog: rzg2l_wdt: Fix &amp;#39;BUG: Invalid wait context&amp;#39;&lt;/p&gt;
&lt;p&gt;This patch fixes the issue &amp;#39;BUG: Invalid wait context&amp;#39; during restart()
callback by using clk_prepare_enable() instead of pm_runtime_get_sync()
for turning on the clocks during restart.&lt;/p&gt;
&lt;p&gt;This issue is noticed when testing with renesas_defconfig.&lt;/p&gt;
&lt;p&gt;[   42.213802] reboot: Restarting system
[   42.217860]
[   42.219364] =============================
[   42.223368] [ BUG: Invalid wait context ]
[   42.227372] 5.17.0-rc5-arm64-renesas-00002-g10393723e35e #522 Not tainted
[   42.234153] -----------------------------
[   42.238155] systemd-shutdow/1 is trying to lock:
[   42.242766] ffff00000a650828 (&amp;amp;genpd-&amp;gt;mlock){+.+.}-{3:3}, at: genpd_lock_mtx+0x14/0x20
[   42.250709] other info that might help us debug this:
[   42.255753] context-{4:4}
[   42.258368] 2 locks held by systemd-shutdow/1:
[   42.262806]  #0: ffff80000944e1c8 (system_transition_mutex#2){+.+.}-{3:3}, at: __do_sys_reboot+0xd0/0x250
[   42.272388]  #1: ffff8000094c4e40 (rcu_read_lock){....}-{1:2}, at: atomic_notifier_call_chain+0x0/0x150
[   42.281795] stack backtrace:
[   42.284672] CPU: 0 PID: 1 Comm: systemd-shutdow Not tainted 5.17.0-rc5-arm64-renesas-00002-g10393723e35e #522
[   42.294577] Hardware name: Renesas SMARC EVK based on r9a07g044c2 (DT)
[   42.301096] Call trace:
[   42.303538]  dump_backtrace+0xcc/0xd8
[   42.307203]  show_stack+0x14/0x30
[   42.310517]  dump_stack_lvl+0x88/0xb0
[…&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;watchdog: rzg2l_wdt: Fix &amp;#39;BUG: Invalid wait context&amp;#39;&lt;/p&gt;
&lt;p&gt;This patch fixes the issue &amp;#39;BUG: Invalid wait context&amp;#39; during restart()
callback by using clk_prepare_enable() instead of pm_runtime_get_sync()
for turning on the clocks during restart.&lt;/p&gt;
&lt;p&gt;This issue is noticed when testing with renesas_defconfig.&lt;/p&gt;
&lt;p&gt;[   42.213802] reboot: Restarting system
[   42.217860]
[   42.219364] =============================
[   42.223368] [ BUG: Invalid wait context ]
[   42.227372] 5.17.0-rc5-arm64-renesas-00002-g10393723e35e #522 Not tainted
[   42.234153] -----------------------------
[   42.238155] systemd-shutdow/1 is trying to lock:
[   42.242766] ffff00000a650828 (&amp;amp;genpd-&amp;gt;mlock){+.+.}-{3:3}, at: genpd_lock_mtx+0x14/0x20
[   42.250709] other info that might help us debug this:
[   42.255753] context-{4:4}
[   42.258368] 2 locks held by systemd-shutdow/1:
[   42.262806]  #0: ffff80000944e1c8 (system_transition_mutex#2){+.+.}-{3:3}, at: __do_sys_reboot+0xd0/0x250
[   42.272388]  #1: ffff8000094c4e40 (rcu_read_lock){....}-{1:2}, at: atomic_notifier_call_chain+0x0/0x150
[   42.281795] stack backtrace:
[   42.284672] CPU: 0 PID: 1 Comm: systemd-shutdow Not tainted 5.17.0-rc5-arm64-renesas-00002-g10393723e35e #522
[   42.294577] Hardware name: Renesas SMARC EVK based on r9a07g044c2 (DT)
[   42.301096] Call trace:
[   42.303538]  dump_backtrace+0xcc/0xd8
[   42.307203]  show_stack+0x14/0x30
[   42.310517]  dump_stack_lvl+0x88/0xb0
[…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-h447-c2wm-jgwc</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-49383</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49383</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 69 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: watchdog: rzg2l_wdt: Fix &amp;#39;BUG: Invalid wait context&amp;#39; This patch fixes the issue &amp;#39;BUG: Invalid wait context&amp;#39; during restart() callback by using clk_prepare_enable() instead of pm_runtime_get_sync() for turning on the clocks during restart. This issue is noticed when testing with renesas_defconfig. [   42.213802] reboot: Restarting system [   42.217860] [   42.219364] ============================= [   42.223368] [ BUG: Invalid wait context ] [   42.227372] 5.17.0-rc5-arm64-renesas-00002-g10393723e35e #522 Not tainted [   42.234153] ----------------------------- [   42.238155] systemd-shutdow/1 is trying to lock: [   42.242766] ffff00000a650828 (&amp;amp;genpd-&amp;gt;mlock){+.+.}-{3:3}, at: genpd_lock_mtx+0x14/0x20 [   42.250709] other info that might help us debug this: [   42.255753] context-{4:4} [   42.258368] 2 locks held by systemd-shutdow/1: [   42.262806]  #0: ffff80000944e1c8 (system_transition_mutex#2){+.+.}-{3:3}, at: __do_sys_reboot+0xd0/0x250 [   42.272388]  #1: ffff8000094c4e40 (rcu_read_lock){....}-{1:2}, at: atomic_notifier_call_chain+0x0/0x150 [   42.281795] stack backtrace: [   42.284672] CPU: 0 PID: 1 Comm: systemd-shutdow Not tainted 5.17.0-rc5-arm64-renesas-00002-g10393723e35e #522 [   42.294577] Hardware name: Renesas SMARC EVK based on r9a07g044c2 (DT) [   42.301096] Call trace: [   42.303538]  dump_backtrace+0xcc/0xd8 [   42.307203]  show_stack+0x14/0x30 [   42.310517]  dump_stack_lvl+0x88/0xb0 [   42…&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 69 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: watchdog: rzg2l_wdt: Fix &amp;#39;BUG: Invalid wait context&amp;#39; This patch fixes the issue &amp;#39;BUG: Invalid wait context&amp;#39; during restart() callback by using clk_prepare_enable() instead of pm_runtime_get_sync() for turning on the clocks during restart. This issue is noticed when testing with renesas_defconfig. [   42.213802] reboot: Restarting system [   42.217860] [   42.219364] ============================= [   42.223368] [ BUG: Invalid wait context ] [   42.227372] 5.17.0-rc5-arm64-renesas-00002-g10393723e35e #522 Not tainted [   42.234153] ----------------------------- [   42.238155] systemd-shutdow/1 is trying to lock: [   42.242766] ffff00000a650828 (&amp;amp;genpd-&amp;gt;mlock){+.+.}-{3:3}, at: genpd_lock_mtx+0x14/0x20 [   42.250709] other info that might help us debug this: [   42.255753] context-{4:4} [   42.258368] 2 locks held by systemd-shutdow/1: [   42.262806]  #0: ffff80000944e1c8 (system_transition_mutex#2){+.+.}-{3:3}, at: __do_sys_reboot+0xd0/0x250 [   42.272388]  #1: ffff8000094c4e40 (rcu_read_lock){....}-{1:2}, at: atomic_notifier_call_chain+0x0/0x150 [   42.281795] stack backtrace: [   42.284672] CPU: 0 PID: 1 Comm: systemd-shutdow Not tainted 5.17.0-rc5-arm64-renesas-00002-g10393723e35e #522 [   42.294577] Hardware name: Renesas SMARC EVK based on r9a07g044c2 (DT) [   42.301096] Call trace: [   42.303538]  dump_backtrace+0xcc/0xd8 [   42.307203]  show_stack+0x14/0x30 [   42.310517]  dump_stack_lvl+0x88/0xb0 [   42…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49383</guid>
    </item>
  </channel>
</rss>
