<?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-29T19:20:56.905986+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-04331</id>
    <title>bdu:2026-04331</title>
    <updated>2026-09-29T19:20:57.774134+00:00</updated>
    <content>bdu:2026-04331</content>
    <link href="https://db.gcve.eu/vuln/bdu:2026-04331"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/certfr-2025-avi-1009</id>
    <title>certfr-2025-avi-1009 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Elles permettent à un attaquant de provoqu…</title>
    <updated>2026-09-29T19:20:57.774263+00:00</updated>
    <content>certfr-2025-avi-1009</content>
    <link href="https://db.gcve.eu/vuln/certfr-2025-avi-1009"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2023-53611</id>
    <title>fkie_cve-2023-53611</title>
    <updated>2026-09-29T19:20:57.774287+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>ipmi_si: fix a memleak in try_smi_init()</p>
<p>Kmemleak reported the following leak info in try_smi_init():</p>
<p>unreferenced object 0xffff00018ecf9400 (size 1024):
  comm "modprobe", pid 2707763, jiffies 4300851415 (age 773.308s)
  backtrace:
    [&lt;000000004ca5b312&gt;] __kmalloc+0x4b8/0x7b0
    [&lt;00000000953b1072&gt;] try_smi_init+0x148/0x5dc [ipmi_si]
    [&lt;000000006460d325&gt;] 0xffff800081b10148
    [&lt;0000000039206ea5&gt;] do_one_initcall+0x64/0x2a4
    [&lt;00000000601399ce&gt;] do_init_module+0x50/0x300
    [&lt;000000003c12ba3c&gt;] load_module+0x7a8/0x9e0
    [&lt;00000000c246fffe&gt;] __se_sys_init_module+0x104/0x180
    [&lt;00000000eea99093&gt;] __arm64_sys_init_module+0x24/0x30
    [&lt;0000000021b1ef87&gt;] el0_svc_common.constprop.0+0x94/0x250
    [&lt;0000000070f4f8b7&gt;] do_el0_svc+0x48/0xe0
    [&lt;000000005a05337f&gt;] el0_svc+0x24/0x3c
    [&lt;000000005eb248d6&gt;] el0_sync_handler+0x160/0x164
    [&lt;0000000030a59039&gt;] el0_sync+0x160/0x180</p>
<p>The problem was that when an error occurred before handlers registration
and after allocating `new_smi-&gt;si_sm`, the variable wouldn't be freed in
the error handling afterwards since `shutdown_smi()` hadn't been
registered yet. Fix it by adding a `kfree()` in the error handling path
in `try_smi_init()`.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2023-53611"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-7r62-fw3j-xjqf</id>
    <title>GHSA-7r62-fw3j-xjqf</title>
    <updated>2026-09-29T19:20:57.774345+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>ipmi_si: fix a memleak in try_smi_init()</p>
<p>Kmemleak reported the following leak info in try_smi_init():</p>
<p>unreferenced object 0xffff00018ecf9400 (size 1024):
  comm "modprobe", pid 2707763, jiffies 4300851415 (age 773.308s)
  backtrace:
    [&lt;000000004ca5b312&gt;] __kmalloc+0x4b8/0x7b0
    [&lt;00000000953b1072&gt;] try_smi_init+0x148/0x5dc [ipmi_si]
    [&lt;000000006460d325&gt;] 0xffff800081b10148
    [&lt;0000000039206ea5&gt;] do_one_initcall+0x64/0x2a4
    [&lt;00000000601399ce&gt;] do_init_module+0x50/0x300
    [&lt;000000003c12ba3c&gt;] load_module+0x7a8/0x9e0
    [&lt;00000000c246fffe&gt;] __se_sys_init_module+0x104/0x180
    [&lt;00000000eea99093&gt;] __arm64_sys_init_module+0x24/0x30
    [&lt;0000000021b1ef87&gt;] el0_svc_common.constprop.0+0x94/0x250
    [&lt;0000000070f4f8b7&gt;] do_el0_svc+0x48/0xe0
    [&lt;000000005a05337f&gt;] el0_svc+0x24/0x3c
    [&lt;000000005eb248d6&gt;] el0_sync_handler+0x160/0x164
    [&lt;0000000030a59039&gt;] el0_sync+0x160/0x180</p>
<p>The problem was that when an error occurred before handlers registration
and after allocating `new_smi-&gt;si_sm`, the variable wouldn't be freed in
the error handling afterwards since `shutdown_smi()` hadn't been
registered yet. Fix it by adding a `kfree()` in the error handling path
in `try_smi_init()`.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-7r62-fw3j-xjqf"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/rhsa-2024:2394</id>
    <title>RHSA-2024:2394 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
    <updated>2026-09-29T19:20:57.774376+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>kernel: Bluetooth BR/EDR PIN Pairing procedure is vulnerable to an impersonation attack kernel: ovl: fix warning in ovl_create_real() kernel: memcg does not limit the number of POSIX file locks allowing memory exhaustion kernel: vmwgfx: NULL pointer dereference in vmw_cmd_dx_define_query kernel: integer overflow in l2cap_config_req() in net/bluetooth/l2cap_core.c kernel: i2c: mlxbf: prevent stack overflow in mlxbf_i2c_smbus_start_transaction() kernel: Bluetooth: L2CAP: Fix u8 overflow kernel: hwmon: (coretemp) fix pci device refcount leak in nv1a_ram_new() kernel: tracing: Fix sleeping function called from invalid context on RT kernel kernel: net: mdio: unexport __init-annotated mdio_bus_init() kernel: arm64: ftrace: consistently handle PLTs. kernel: mm/uffd: fix pte marker when fork() without fork event kernel: Bluetooth: Fix a buffer overflow in mgmt_mesh_add() kernel: tty: n_gsm: add sanity check for gsm-&gt;receive in gsm_receive_buf() kernel: ftrace: Fix NULL pointer dereference in is_ftrace_trampoline when ftrace is dead kernel: tee: add overflow check in register_shm_helper() kernel: tty: n_gsm: fix deadlock and link starvation in outgoing data path kernel: PM: hibernate: defer device probing when resuming from hibernation kernel: ext4: don't allow journal inode to have encrypt flag kernel: ext4: fix delayed allocation bug in ext4_clu_mapped for bigalloc + inline kernel: erofs: fix order &gt;= MAX_ORDER warning due to crafted negative i_size kernel: perf/x86/intel/uncore: F…</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/rhsa-2024:2394"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/suse-su-2025:21040-1</id>
    <title>SUSE-SU-2025:21040-1 — Security update for the Linux Kernel</title>
    <updated>2026-09-29T19:20:57.775362+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Security update for the Linux Kernel</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/suse-su-2025:21040-1"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ubuntu-cve-2023-53611</id>
    <title>UBUNTU-CVE-2023-53611</title>
    <updated>2026-09-29T19:20:57.775553+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: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 141 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: ipmi_si: fix a memleak in try_smi_init() Kmemleak reported the following leak info in try_smi_init(): unreferenced object 0xffff00018ecf9400 (size 1024):   comm "modprobe", pid 2707763, jiffies 4300851415 (age 773.308s)   backtrace:     [&lt;000000004ca5b312&gt;] __kmalloc+0x4b8/0x7b0     [&lt;00000000953b1072&gt;] try_smi_init+0x148/0x5dc [ipmi_si]     [&lt;000000006460d325&gt;] 0xffff800081b10148     [&lt;0000000039206ea5&gt;] do_one_initcall+0x64/0x2a4     [&lt;00000000601399ce&gt;] do_init_module+0x50/0x300     [&lt;000000003c12ba3c&gt;] load_module+0x7a8/0x9e0     [&lt;00000000c246fffe&gt;] __se_sys_init_module+0x104/0x180     [&lt;00000000eea99093&gt;] __arm64_sys_init_module+0x24/0x30     [&lt;0000000021b1ef87&gt;] el0_svc_common.constprop.0+0x94/0x250     [&lt;0000000070f4f8b7&gt;] do_el0_svc+0x48/0xe0     [&lt;000000005a05337f&gt;] el0_svc+0x24/0x3c     [&lt;000000005eb248d6&gt;] el0_sync_handler+0x160/0x164     [&lt;0000000030a59039&gt;] el0_sync+0x160/0x180 The problem was that when an error occurred before handlers registration and after allocating `new_smi-&gt;si_sm`, the variable wouldn't be freed in the error handling afterwards since `shutdown_smi()` hadn't been registered yet. Fix it by adding a `kfree()` in the error handling path in `try_smi_init()`.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ubuntu-cve-2023-53611"/>
  </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-29T19:20:57.775909+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>
