<?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, 29 Sep 2026 07:43:49 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-02272</title>
      <link>https://db.gcve.eu/vuln/bdu:2026-02272</link>
      <description>bdu:2026-02272</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/bdu:2026-02272</guid>
    </item>
    <item>
      <title>fkie_cve-2022-50477</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2022-50477</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;rtc: class: Fix potential memleak in devm_rtc_allocate_device()&lt;/p&gt;
&lt;p&gt;devm_rtc_allocate_device() will alloc a rtc_device first, and then run
dev_set_name(). If dev_set_name() failed, the rtc_device will memleak.
Move devm_add_action_or_reset() in front of dev_set_name() to prevent
memleak.&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff888110a53000 (size 2048):
  comm &amp;#34;python3&amp;#34;, pid 470, jiffies 4296078308 (age 58.882s)
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 08 30 a5 10 81 88 ff ff  .........0......
    08 30 a5 10 81 88 ff ff 00 00 00 00 00 00 00 00  .0..............
  backtrace:
    [&amp;lt;000000004aac0364&amp;gt;] kmalloc_trace+0x21/0x110
    [&amp;lt;000000000ff02202&amp;gt;] devm_rtc_allocate_device+0xd4/0x400
    [&amp;lt;000000001bdf5639&amp;gt;] devm_rtc_device_register+0x1a/0x80
    [&amp;lt;00000000351bf81c&amp;gt;] rx4581_probe+0xdd/0x110 [rtc_rx4581]
    [&amp;lt;00000000f0eba0ae&amp;gt;] spi_probe+0xde/0x130
    [&amp;lt;00000000bff89ee8&amp;gt;] really_probe+0x175/0x3f0
    [&amp;lt;00000000128e8d84&amp;gt;] __driver_probe_device+0xe6/0x170
    [&amp;lt;00000000ee5bf913&amp;gt;] device_driver_attach+0x32/0x80
    [&amp;lt;00000000f3f28f92&amp;gt;] bind_store+0x10b/0x1a0
    [&amp;lt;000000009ff812d8&amp;gt;] drv_attr_store+0x49/0x70
    [&amp;lt;000000008139c323&amp;gt;] sysfs_kf_write+0x8d/0xb0
    [&amp;lt;00000000b6146e01&amp;gt;] kernfs_fop_write_iter+0x214/0x2d0
    [&amp;lt;00000000ecbe3895&amp;gt;] vfs_write+0x61a/0x7d0
    [&amp;lt;00000000aa2196ea&amp;gt;] ksys_write+0xc8/0x190
    [&amp;lt;0000000046a600f5&amp;gt;] do_syscall_64+0x37/0x90
    [&amp;lt;00000000541a336f&amp;gt;] entry_SYSCALL_64_after_hwframe+…&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: class: Fix potential memleak in devm_rtc_allocate_device()&lt;/p&gt;
&lt;p&gt;devm_rtc_allocate_device() will alloc a rtc_device first, and then run
dev_set_name(). If dev_set_name() failed, the rtc_device will memleak.
Move devm_add_action_or_reset() in front of dev_set_name() to prevent
memleak.&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff888110a53000 (size 2048):
  comm &amp;#34;python3&amp;#34;, pid 470, jiffies 4296078308 (age 58.882s)
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 08 30 a5 10 81 88 ff ff  .........0......
    08 30 a5 10 81 88 ff ff 00 00 00 00 00 00 00 00  .0..............
  backtrace:
    [&amp;lt;000000004aac0364&amp;gt;] kmalloc_trace+0x21/0x110
    [&amp;lt;000000000ff02202&amp;gt;] devm_rtc_allocate_device+0xd4/0x400
    [&amp;lt;000000001bdf5639&amp;gt;] devm_rtc_device_register+0x1a/0x80
    [&amp;lt;00000000351bf81c&amp;gt;] rx4581_probe+0xdd/0x110 [rtc_rx4581]
    [&amp;lt;00000000f0eba0ae&amp;gt;] spi_probe+0xde/0x130
    [&amp;lt;00000000bff89ee8&amp;gt;] really_probe+0x175/0x3f0
    [&amp;lt;00000000128e8d84&amp;gt;] __driver_probe_device+0xe6/0x170
    [&amp;lt;00000000ee5bf913&amp;gt;] device_driver_attach+0x32/0x80
    [&amp;lt;00000000f3f28f92&amp;gt;] bind_store+0x10b/0x1a0
    [&amp;lt;000000009ff812d8&amp;gt;] drv_attr_store+0x49/0x70
    [&amp;lt;000000008139c323&amp;gt;] sysfs_kf_write+0x8d/0xb0
    [&amp;lt;00000000b6146e01&amp;gt;] kernfs_fop_write_iter+0x214/0x2d0
    [&amp;lt;00000000ecbe3895&amp;gt;] vfs_write+0x61a/0x7d0
    [&amp;lt;00000000aa2196ea&amp;gt;] ksys_write+0xc8/0x190
    [&amp;lt;0000000046a600f5&amp;gt;] do_syscall_64+0x37/0x90
    [&amp;lt;00000000541a336f&amp;gt;] entry_SYSCALL_64_after_hwframe+…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2022-50477</guid>
    </item>
    <item>
      <title>GHSA-wq62-9p2f-cfr9</title>
      <link>https://db.gcve.eu/vuln/ghsa-wq62-9p2f-cfr9</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;rtc: class: Fix potential memleak in devm_rtc_allocate_device()&lt;/p&gt;
&lt;p&gt;devm_rtc_allocate_device() will alloc a rtc_device first, and then run
dev_set_name(). If dev_set_name() failed, the rtc_device will memleak.
Move devm_add_action_or_reset() in front of dev_set_name() to prevent
memleak.&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff888110a53000 (size 2048):
  comm &amp;#34;python3&amp;#34;, pid 470, jiffies 4296078308 (age 58.882s)
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 08 30 a5 10 81 88 ff ff  .........0......
    08 30 a5 10 81 88 ff ff 00 00 00 00 00 00 00 00  .0..............
  backtrace:
    [&amp;lt;000000004aac0364&amp;gt;] kmalloc_trace+0x21/0x110
    [&amp;lt;000000000ff02202&amp;gt;] devm_rtc_allocate_device+0xd4/0x400
    [&amp;lt;000000001bdf5639&amp;gt;] devm_rtc_device_register+0x1a/0x80
    [&amp;lt;00000000351bf81c&amp;gt;] rx4581_probe+0xdd/0x110 [rtc_rx4581]
    [&amp;lt;00000000f0eba0ae&amp;gt;] spi_probe+0xde/0x130
    [&amp;lt;00000000bff89ee8&amp;gt;] really_probe+0x175/0x3f0
    [&amp;lt;00000000128e8d84&amp;gt;] __driver_probe_device+0xe6/0x170
    [&amp;lt;00000000ee5bf913&amp;gt;] device_driver_attach+0x32/0x80
    [&amp;lt;00000000f3f28f92&amp;gt;] bind_store+0x10b/0x1a0
    [&amp;lt;000000009ff812d8&amp;gt;] drv_attr_store+0x49/0x70
    [&amp;lt;000000008139c323&amp;gt;] sysfs_kf_write+0x8d/0xb0
    [&amp;lt;00000000b6146e01&amp;gt;] kernfs_fop_write_iter+0x214/0x2d0
    [&amp;lt;00000000ecbe3895&amp;gt;] vfs_write+0x61a/0x7d0
    [&amp;lt;00000000aa2196ea&amp;gt;] ksys_write+0xc8/0x190
    [&amp;lt;0000000046a600f5&amp;gt;] do_syscall_64+0x37/0x90
    [&amp;lt;00000000541a336f&amp;gt;] entry_SYSCALL_64_after_hwframe+…&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: class: Fix potential memleak in devm_rtc_allocate_device()&lt;/p&gt;
&lt;p&gt;devm_rtc_allocate_device() will alloc a rtc_device first, and then run
dev_set_name(). If dev_set_name() failed, the rtc_device will memleak.
Move devm_add_action_or_reset() in front of dev_set_name() to prevent
memleak.&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff888110a53000 (size 2048):
  comm &amp;#34;python3&amp;#34;, pid 470, jiffies 4296078308 (age 58.882s)
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 08 30 a5 10 81 88 ff ff  .........0......
    08 30 a5 10 81 88 ff ff 00 00 00 00 00 00 00 00  .0..............
  backtrace:
    [&amp;lt;000000004aac0364&amp;gt;] kmalloc_trace+0x21/0x110
    [&amp;lt;000000000ff02202&amp;gt;] devm_rtc_allocate_device+0xd4/0x400
    [&amp;lt;000000001bdf5639&amp;gt;] devm_rtc_device_register+0x1a/0x80
    [&amp;lt;00000000351bf81c&amp;gt;] rx4581_probe+0xdd/0x110 [rtc_rx4581]
    [&amp;lt;00000000f0eba0ae&amp;gt;] spi_probe+0xde/0x130
    [&amp;lt;00000000bff89ee8&amp;gt;] really_probe+0x175/0x3f0
    [&amp;lt;00000000128e8d84&amp;gt;] __driver_probe_device+0xe6/0x170
    [&amp;lt;00000000ee5bf913&amp;gt;] device_driver_attach+0x32/0x80
    [&amp;lt;00000000f3f28f92&amp;gt;] bind_store+0x10b/0x1a0
    [&amp;lt;000000009ff812d8&amp;gt;] drv_attr_store+0x49/0x70
    [&amp;lt;000000008139c323&amp;gt;] sysfs_kf_write+0x8d/0xb0
    [&amp;lt;00000000b6146e01&amp;gt;] kernfs_fop_write_iter+0x214/0x2d0
    [&amp;lt;00000000ecbe3895&amp;gt;] vfs_write+0x61a/0x7d0
    [&amp;lt;00000000aa2196ea&amp;gt;] ksys_write+0xc8/0x190
    [&amp;lt;0000000046a600f5&amp;gt;] do_syscall_64+0x37/0x90
    [&amp;lt;00000000541a336f&amp;gt;] entry_SYSCALL_64_after_hwframe+…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-wq62-9p2f-cfr9</guid>
    </item>
    <item>
      <title>RHSA-2023:6583 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
      <link>https://db.gcve.eu/vuln/rhsa-2023:6583</link>
      <description>&lt;p&gt;kernel: seg6: fix the iif in the IPv6 socket control block Kernel: race when faulting a device private page in memory manager kernel: use-after-free in l1oip timer handlers kernel: Rate limit overflow messages in r8152 in intr_callback kernel: vmwgfx: use-after-free in vmw_cmd_res_check kernel: vmwgfx: use-after-free in vmw_execbuf_tie_context hw: Intel: Gather Data Sampling (GDS) side channel vulnerability kernel: Information leak in l2cap_parse_conf_req in net/bluetooth/l2cap_core.c kernel: perf: Fix perf_pending_task() UaF kernel: gpiolib: fix memory leak in gpiochip_setup_dev() kernel: memcg: fix possible use-after-free in memcg_write_event_control() kernel: mm/khugepaged: invoke MMU notifiers in shmem/file collapse paths kernel: char: tpm: Protect tpm_pm_suspend with locks kernel: ixgbevf: Fix resource leak in ixgbevf_init_module() kernel: dax: make sure inodes are flushed before destroy cache kernel: watch_queue: Actually free the watch kernel: watch_queue: Fix NULL dereference in error cleanup kernel: rtc: pl031: fix rtc features null pointer dereference kernel: tpm: fix reference counting for struct tpm_chip kernel: NFSv4: Don&amp;#39;t hold the layoutget locks across multiple RPC calls kernel: xprtrdma: treat all calls not a bcall when bc_serv is NULL kernel: net: ipv6: unexport __init-annotated seg6_hmac_init() kernel: af_unix: Fix a data-race in unix_dgram_peer_wake_me(). kernel: regulator: scmi: Fix refcount leak in scmi_regulator_probe kernel: mm/mempolicy: fix uninit-v…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: seg6: fix the iif in the IPv6 socket control block Kernel: race when faulting a device private page in memory manager kernel: use-after-free in l1oip timer handlers kernel: Rate limit overflow messages in r8152 in intr_callback kernel: vmwgfx: use-after-free in vmw_cmd_res_check kernel: vmwgfx: use-after-free in vmw_execbuf_tie_context hw: Intel: Gather Data Sampling (GDS) side channel vulnerability kernel: Information leak in l2cap_parse_conf_req in net/bluetooth/l2cap_core.c kernel: perf: Fix perf_pending_task() UaF kernel: gpiolib: fix memory leak in gpiochip_setup_dev() kernel: memcg: fix possible use-after-free in memcg_write_event_control() kernel: mm/khugepaged: invoke MMU notifiers in shmem/file collapse paths kernel: char: tpm: Protect tpm_pm_suspend with locks kernel: ixgbevf: Fix resource leak in ixgbevf_init_module() kernel: dax: make sure inodes are flushed before destroy cache kernel: watch_queue: Actually free the watch kernel: watch_queue: Fix NULL dereference in error cleanup kernel: rtc: pl031: fix rtc features null pointer dereference kernel: tpm: fix reference counting for struct tpm_chip kernel: NFSv4: Don&amp;#39;t hold the layoutget locks across multiple RPC calls kernel: xprtrdma: treat all calls not a bcall when bc_serv is NULL kernel: net: ipv6: unexport __init-annotated seg6_hmac_init() kernel: af_unix: Fix a data-race in unix_dgram_peer_wake_me(). kernel: regulator: scmi: Fix refcount leak in scmi_regulator_probe kernel: mm/mempolicy: fix uninit-v…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/rhsa-2023:6583</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-50477</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2022-50477</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 78 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: rtc: class: Fix potential memleak in devm_rtc_allocate_device() devm_rtc_allocate_device() will alloc a rtc_device first, and then run dev_set_name(). If dev_set_name() failed, the rtc_device will memleak. Move devm_add_action_or_reset() in front of dev_set_name() to prevent memleak. unreferenced object 0xffff888110a53000 (size 2048):   comm &amp;#34;python3&amp;#34;, pid 470, jiffies 4296078308 (age 58.882s)   hex dump (first 32 bytes):     00 00 00 00 00 00 00 00 08 30 a5 10 81 88 ff ff  .........0......     08 30 a5 10 81 88 ff ff 00 00 00 00 00 00 00 00  .0..............   backtrace:     [&amp;lt;000000004aac0364&amp;gt;] kmalloc_trace+0x21/0x110     [&amp;lt;000000000ff02202&amp;gt;] devm_rtc_allocate_device+0xd4/0x400     [&amp;lt;000000001bdf5639&amp;gt;] devm_rtc_device_register+0x1a/0x80     [&amp;lt;00000000351bf81c&amp;gt;] rx4581_probe+0xdd/0x110 [rtc_rx4581]     [&amp;lt;00000000f0eba0ae&amp;gt;] spi_probe+0xde/0x130     [&amp;lt;00000000bff89ee8&amp;gt;] really_probe+0x175/0x3f0     [&amp;lt;00000000128e8d84&amp;gt;] __driver_probe_device+0xe6/0x170     [&amp;lt;00000000ee5bf913&amp;gt;] device_driver_attach+0x32/0x80     [&amp;lt;00000000f3f28f92&amp;gt;] bind_store+0x10b/0x1a0     [&amp;lt;000000009ff812d8&amp;gt;] drv_attr_store+0x49/0x70     [&amp;lt;000000008139c323&amp;gt;] sysfs_kf_write+0x8d/0xb0     [&amp;lt;00000000b6146e01&amp;gt;] kernfs_fop_write_iter+0x214/0x2d0     [&amp;lt;00000000ecbe3895&amp;gt;] vfs_write+0x61a/0x7d0     [&amp;lt;00000000aa2196ea&amp;gt;] ksys_write+0xc8/0x190     [&amp;lt;0000000046a600f5&amp;gt;] do_syscall_64+0x37/0x90     [&amp;lt;00000000541a336f&amp;gt;] entry_SYSCALL_64_after_hwframe+0x6…&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 78 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: rtc: class: Fix potential memleak in devm_rtc_allocate_device() devm_rtc_allocate_device() will alloc a rtc_device first, and then run dev_set_name(). If dev_set_name() failed, the rtc_device will memleak. Move devm_add_action_or_reset() in front of dev_set_name() to prevent memleak. unreferenced object 0xffff888110a53000 (size 2048):   comm &amp;#34;python3&amp;#34;, pid 470, jiffies 4296078308 (age 58.882s)   hex dump (first 32 bytes):     00 00 00 00 00 00 00 00 08 30 a5 10 81 88 ff ff  .........0......     08 30 a5 10 81 88 ff ff 00 00 00 00 00 00 00 00  .0..............   backtrace:     [&amp;lt;000000004aac0364&amp;gt;] kmalloc_trace+0x21/0x110     [&amp;lt;000000000ff02202&amp;gt;] devm_rtc_allocate_device+0xd4/0x400     [&amp;lt;000000001bdf5639&amp;gt;] devm_rtc_device_register+0x1a/0x80     [&amp;lt;00000000351bf81c&amp;gt;] rx4581_probe+0xdd/0x110 [rtc_rx4581]     [&amp;lt;00000000f0eba0ae&amp;gt;] spi_probe+0xde/0x130     [&amp;lt;00000000bff89ee8&amp;gt;] really_probe+0x175/0x3f0     [&amp;lt;00000000128e8d84&amp;gt;] __driver_probe_device+0xe6/0x170     [&amp;lt;00000000ee5bf913&amp;gt;] device_driver_attach+0x32/0x80     [&amp;lt;00000000f3f28f92&amp;gt;] bind_store+0x10b/0x1a0     [&amp;lt;000000009ff812d8&amp;gt;] drv_attr_store+0x49/0x70     [&amp;lt;000000008139c323&amp;gt;] sysfs_kf_write+0x8d/0xb0     [&amp;lt;00000000b6146e01&amp;gt;] kernfs_fop_write_iter+0x214/0x2d0     [&amp;lt;00000000ecbe3895&amp;gt;] vfs_write+0x61a/0x7d0     [&amp;lt;00000000aa2196ea&amp;gt;] ksys_write+0xc8/0x190     [&amp;lt;0000000046a600f5&amp;gt;] do_syscall_64+0x37/0x90     [&amp;lt;00000000541a336f&amp;gt;] entry_SYSCALL_64_after_hwframe+0x6…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2022-50477</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2194 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2025-2194</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2025-2194</guid>
    </item>
  </channel>
</rss>
