<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T07:43:48.747490+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/bdu:2026-02272</id>
    <title>bdu:2026-02272</title>
    <updated>2026-09-29T07:43:48.995050+00:00</updated>
    <content>bdu:2026-02272</content>
    <link href="https://db.gcve.eu/vuln/bdu:2026-02272"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2022-50477</id>
    <title>fkie_cve-2022-50477</title>
    <updated>2026-09-29T07:43:48.995103+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>rtc: class: Fix potential memleak in devm_rtc_allocate_device()</p>
<p>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.</p>
<p>unreferenced object 0xffff888110a53000 (size 2048):
  comm "python3", 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:
    [&lt;000000004aac0364&gt;] kmalloc_trace+0x21/0x110
    [&lt;000000000ff02202&gt;] devm_rtc_allocate_device+0xd4/0x400
    [&lt;000000001bdf5639&gt;] devm_rtc_device_register+0x1a/0x80
    [&lt;00000000351bf81c&gt;] rx4581_probe+0xdd/0x110 [rtc_rx4581]
    [&lt;00000000f0eba0ae&gt;] spi_probe+0xde/0x130
    [&lt;00000000bff89ee8&gt;] really_probe+0x175/0x3f0
    [&lt;00000000128e8d84&gt;] __driver_probe_device+0xe6/0x170
    [&lt;00000000ee5bf913&gt;] device_driver_attach+0x32/0x80
    [&lt;00000000f3f28f92&gt;] bind_store+0x10b/0x1a0
    [&lt;000000009ff812d8&gt;] drv_attr_store+0x49/0x70
    [&lt;000000008139c323&gt;] sysfs_kf_write+0x8d/0xb0
    [&lt;00000000b6146e01&gt;] kernfs_fop_write_iter+0x214/0x2d0
    [&lt;00000000ecbe3895&gt;] vfs_write+0x61a/0x7d0
    [&lt;00000000aa2196ea&gt;] ksys_write+0xc8/0x190
    [&lt;0000000046a600f5&gt;] do_syscall_64+0x37/0x90
    [&lt;00000000541a336f&gt;] entry_SYSCALL_64_after_hwframe+…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2022-50477"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-wq62-9p2f-cfr9</id>
    <title>GHSA-wq62-9p2f-cfr9</title>
    <updated>2026-09-29T07:43:48.995177+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>rtc: class: Fix potential memleak in devm_rtc_allocate_device()</p>
<p>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.</p>
<p>unreferenced object 0xffff888110a53000 (size 2048):
  comm "python3", 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:
    [&lt;000000004aac0364&gt;] kmalloc_trace+0x21/0x110
    [&lt;000000000ff02202&gt;] devm_rtc_allocate_device+0xd4/0x400
    [&lt;000000001bdf5639&gt;] devm_rtc_device_register+0x1a/0x80
    [&lt;00000000351bf81c&gt;] rx4581_probe+0xdd/0x110 [rtc_rx4581]
    [&lt;00000000f0eba0ae&gt;] spi_probe+0xde/0x130
    [&lt;00000000bff89ee8&gt;] really_probe+0x175/0x3f0
    [&lt;00000000128e8d84&gt;] __driver_probe_device+0xe6/0x170
    [&lt;00000000ee5bf913&gt;] device_driver_attach+0x32/0x80
    [&lt;00000000f3f28f92&gt;] bind_store+0x10b/0x1a0
    [&lt;000000009ff812d8&gt;] drv_attr_store+0x49/0x70
    [&lt;000000008139c323&gt;] sysfs_kf_write+0x8d/0xb0
    [&lt;00000000b6146e01&gt;] kernfs_fop_write_iter+0x214/0x2d0
    [&lt;00000000ecbe3895&gt;] vfs_write+0x61a/0x7d0
    [&lt;00000000aa2196ea&gt;] ksys_write+0xc8/0x190
    [&lt;0000000046a600f5&gt;] do_syscall_64+0x37/0x90
    [&lt;00000000541a336f&gt;] entry_SYSCALL_64_after_hwframe+…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-wq62-9p2f-cfr9"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/rhsa-2023:6583</id>
    <title>RHSA-2023:6583 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
    <updated>2026-09-29T07:43:48.995211+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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'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…</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/rhsa-2023:6583"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ubuntu-cve-2022-50477</id>
    <title>UBUNTU-CVE-2022-50477</title>
    <updated>2026-09-29T07:43:48.996274+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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</p>
<p>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 "python3", 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:     [&lt;000000004aac0364&gt;] kmalloc_trace+0x21/0x110     [&lt;000000000ff02202&gt;] devm_rtc_allocate_device+0xd4/0x400     [&lt;000000001bdf5639&gt;] devm_rtc_device_register+0x1a/0x80     [&lt;00000000351bf81c&gt;] rx4581_probe+0xdd/0x110 [rtc_rx4581]     [&lt;00000000f0eba0ae&gt;] spi_probe+0xde/0x130     [&lt;00000000bff89ee8&gt;] really_probe+0x175/0x3f0     [&lt;00000000128e8d84&gt;] __driver_probe_device+0xe6/0x170     [&lt;00000000ee5bf913&gt;] device_driver_attach+0x32/0x80     [&lt;00000000f3f28f92&gt;] bind_store+0x10b/0x1a0     [&lt;000000009ff812d8&gt;] drv_attr_store+0x49/0x70     [&lt;000000008139c323&gt;] sysfs_kf_write+0x8d/0xb0     [&lt;00000000b6146e01&gt;] kernfs_fop_write_iter+0x214/0x2d0     [&lt;00000000ecbe3895&gt;] vfs_write+0x61a/0x7d0     [&lt;00000000aa2196ea&gt;] ksys_write+0xc8/0x190     [&lt;0000000046a600f5&gt;] do_syscall_64+0x37/0x90     [&lt;00000000541a336f&gt;] entry_SYSCALL_64_after_hwframe+0x6…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ubuntu-cve-2022-50477"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/wid-sec-w-2025-2194</id>
    <title>WID-SEC-W-2025-2194 — Linux Kernel: Mehrere Schwachstellen</title>
    <updated>2026-09-29T07:43:48.996457+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/wid-sec-w-2025-2194"/>
  </entry>
</feed>
