<?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, 13 Oct 2026 10:00:43 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-02521</title>
      <link>https://db.gcve.eu/vuln/bdu:2026-02521</link>
      <description>bdu:2026-02521</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/bdu:2026-02521</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0895 — 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-2025-avi-0895</link>
      <description>certfr-2025-avi-0895</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/certfr-2025-avi-0895</guid>
    </item>
    <item>
      <title>fkie_cve-2022-50269</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2022-50269</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/vkms: Fix memory leak in vkms_init()&lt;/p&gt;
&lt;p&gt;A memory leak was reported after the vkms module install failed.&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff88810bc28520 (size 16):
  comm &amp;#34;modprobe&amp;#34;, pid 9662, jiffies 4298009455 (age 42.590s)
  hex dump (first 16 bytes):
    01 01 00 64 81 88 ff ff 00 00 dc 0a 81 88 ff ff  ...d............
  backtrace:
    [&amp;lt;00000000e7561ff8&amp;gt;] kmalloc_trace+0x27/0x60
    [&amp;lt;000000000b1954a0&amp;gt;] 0xffffffffc45200a9
    [&amp;lt;00000000abbf1da0&amp;gt;] do_one_initcall+0xd0/0x4f0
    [&amp;lt;000000001505ee87&amp;gt;] do_init_module+0x1a4/0x680
    [&amp;lt;00000000958079ad&amp;gt;] load_module+0x6249/0x7110
    [&amp;lt;00000000117e4696&amp;gt;] __do_sys_finit_module+0x140/0x200
    [&amp;lt;00000000f74b12d2&amp;gt;] do_syscall_64+0x35/0x80
    [&amp;lt;000000008fc6fcde&amp;gt;] entry_SYSCALL_64_after_hwframe+0x46/0xb0&lt;/p&gt;
&lt;p&gt;The reason is that the vkms_init() returns without checking the return
value of vkms_create(), and if the vkms_create() failed, the config
allocated at the beginning of vkms_init() is leaked.&lt;/p&gt;
&lt;p&gt;vkms_init()
   config = kmalloc(...) # config allocated
   ...
   return vkms_create() # vkms_create failed and config is leaked&lt;/p&gt;
&lt;p&gt;Fix this problem by checking return value of vkms_create() and free the
config if error happened.&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;drm/vkms: Fix memory leak in vkms_init()&lt;/p&gt;
&lt;p&gt;A memory leak was reported after the vkms module install failed.&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff88810bc28520 (size 16):
  comm &amp;#34;modprobe&amp;#34;, pid 9662, jiffies 4298009455 (age 42.590s)
  hex dump (first 16 bytes):
    01 01 00 64 81 88 ff ff 00 00 dc 0a 81 88 ff ff  ...d............
  backtrace:
    [&amp;lt;00000000e7561ff8&amp;gt;] kmalloc_trace+0x27/0x60
    [&amp;lt;000000000b1954a0&amp;gt;] 0xffffffffc45200a9
    [&amp;lt;00000000abbf1da0&amp;gt;] do_one_initcall+0xd0/0x4f0
    [&amp;lt;000000001505ee87&amp;gt;] do_init_module+0x1a4/0x680
    [&amp;lt;00000000958079ad&amp;gt;] load_module+0x6249/0x7110
    [&amp;lt;00000000117e4696&amp;gt;] __do_sys_finit_module+0x140/0x200
    [&amp;lt;00000000f74b12d2&amp;gt;] do_syscall_64+0x35/0x80
    [&amp;lt;000000008fc6fcde&amp;gt;] entry_SYSCALL_64_after_hwframe+0x46/0xb0&lt;/p&gt;
&lt;p&gt;The reason is that the vkms_init() returns without checking the return
value of vkms_create(), and if the vkms_create() failed, the config
allocated at the beginning of vkms_init() is leaked.&lt;/p&gt;
&lt;p&gt;vkms_init()
   config = kmalloc(...) # config allocated
   ...
   return vkms_create() # vkms_create failed and config is leaked&lt;/p&gt;
&lt;p&gt;Fix this problem by checking return value of vkms_create() and free the
config if error happened.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2022-50269</guid>
    </item>
    <item>
      <title>GHSA-22jx-v9jm-qjqq</title>
      <link>https://db.gcve.eu/vuln/ghsa-22jx-v9jm-qjqq</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/vkms: Fix memory leak in vkms_init()&lt;/p&gt;
&lt;p&gt;A memory leak was reported after the vkms module install failed.&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff88810bc28520 (size 16):
  comm &amp;#34;modprobe&amp;#34;, pid 9662, jiffies 4298009455 (age 42.590s)
  hex dump (first 16 bytes):
    01 01 00 64 81 88 ff ff 00 00 dc 0a 81 88 ff ff  ...d............
  backtrace:
    [&amp;lt;00000000e7561ff8&amp;gt;] kmalloc_trace+0x27/0x60
    [&amp;lt;000000000b1954a0&amp;gt;] 0xffffffffc45200a9
    [&amp;lt;00000000abbf1da0&amp;gt;] do_one_initcall+0xd0/0x4f0
    [&amp;lt;000000001505ee87&amp;gt;] do_init_module+0x1a4/0x680
    [&amp;lt;00000000958079ad&amp;gt;] load_module+0x6249/0x7110
    [&amp;lt;00000000117e4696&amp;gt;] __do_sys_finit_module+0x140/0x200
    [&amp;lt;00000000f74b12d2&amp;gt;] do_syscall_64+0x35/0x80
    [&amp;lt;000000008fc6fcde&amp;gt;] entry_SYSCALL_64_after_hwframe+0x46/0xb0&lt;/p&gt;
&lt;p&gt;The reason is that the vkms_init() returns without checking the return
value of vkms_create(), and if the vkms_create() failed, the config
allocated at the beginning of vkms_init() is leaked.&lt;/p&gt;
&lt;p&gt;vkms_init()
   config = kmalloc(...) # config allocated
   ...
   return vkms_create() # vkms_create failed and config is leaked&lt;/p&gt;
&lt;p&gt;Fix this problem by checking return value of vkms_create() and free the
config if error happened.&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;drm/vkms: Fix memory leak in vkms_init()&lt;/p&gt;
&lt;p&gt;A memory leak was reported after the vkms module install failed.&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff88810bc28520 (size 16):
  comm &amp;#34;modprobe&amp;#34;, pid 9662, jiffies 4298009455 (age 42.590s)
  hex dump (first 16 bytes):
    01 01 00 64 81 88 ff ff 00 00 dc 0a 81 88 ff ff  ...d............
  backtrace:
    [&amp;lt;00000000e7561ff8&amp;gt;] kmalloc_trace+0x27/0x60
    [&amp;lt;000000000b1954a0&amp;gt;] 0xffffffffc45200a9
    [&amp;lt;00000000abbf1da0&amp;gt;] do_one_initcall+0xd0/0x4f0
    [&amp;lt;000000001505ee87&amp;gt;] do_init_module+0x1a4/0x680
    [&amp;lt;00000000958079ad&amp;gt;] load_module+0x6249/0x7110
    [&amp;lt;00000000117e4696&amp;gt;] __do_sys_finit_module+0x140/0x200
    [&amp;lt;00000000f74b12d2&amp;gt;] do_syscall_64+0x35/0x80
    [&amp;lt;000000008fc6fcde&amp;gt;] entry_SYSCALL_64_after_hwframe+0x46/0xb0&lt;/p&gt;
&lt;p&gt;The reason is that the vkms_init() returns without checking the return
value of vkms_create(), and if the vkms_create() failed, the config
allocated at the beginning of vkms_init() is leaked.&lt;/p&gt;
&lt;p&gt;vkms_init()
   config = kmalloc(...) # config allocated
   ...
   return vkms_create() # vkms_create failed and config is leaked&lt;/p&gt;
&lt;p&gt;Fix this problem by checking return value of vkms_create() and free the
config if error happened.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-22jx-v9jm-qjqq</guid>
    </item>
    <item>
      <title>RHSA-2023:6583 — security update for kernel</title>
      <link>https://db.gcve.eu/vuln/rhsa-2023:6583</link>
      <description>&lt;p&gt;security update for kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;security update for kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/rhsa-2023:6583</guid>
    </item>
    <item>
      <title>RHSA-2025:13961 — Red Hat Security Advisory: kernel-rt security update</title>
      <link>https://db.gcve.eu/vuln/rhsa-2025:13961</link>
      <description>&lt;p&gt;kernel: drm/vkms: Fix memory leak in vkms_init() kernel: drm/vkms: Fix null-ptr-deref in vkms_release() kernel: drm/vkms: Fix use after free and double free on init error kernel: net_sched: ets: Fix double list add in class with netem as child qdisc kernel: Bluetooth: hci_core: Fix use-after-free in vhci_flush()&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: drm/vkms: Fix memory leak in vkms_init() kernel: drm/vkms: Fix null-ptr-deref in vkms_release() kernel: drm/vkms: Fix use after free and double free on init error kernel: net_sched: ets: Fix double list add in class with netem as child qdisc kernel: Bluetooth: hci_core: Fix use-after-free in vhci_flush()&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/rhsa-2025:13961</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:03615-1 — Security update for the Linux Kernel</title>
      <link>https://db.gcve.eu/vuln/suse-su-2025:03615-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-2025:03615-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-50269</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2022-50269</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 106 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/vkms: Fix memory leak in vkms_init() A memory leak was reported after the vkms module install failed. unreferenced object 0xffff88810bc28520 (size 16):   comm &amp;#34;modprobe&amp;#34;, pid 9662, jiffies 4298009455 (age 42.590s)   hex dump (first 16 bytes):     01 01 00 64 81 88 ff ff 00 00 dc 0a 81 88 ff ff  ...d............   backtrace:     [&amp;lt;00000000e7561ff8&amp;gt;] kmalloc_trace+0x27/0x60     [&amp;lt;000000000b1954a0&amp;gt;] 0xffffffffc45200a9     [&amp;lt;00000000abbf1da0&amp;gt;] do_one_initcall+0xd0/0x4f0     [&amp;lt;000000001505ee87&amp;gt;] do_init_module+0x1a4/0x680     [&amp;lt;00000000958079ad&amp;gt;] load_module+0x6249/0x7110     [&amp;lt;00000000117e4696&amp;gt;] __do_sys_finit_module+0x140/0x200     [&amp;lt;00000000f74b12d2&amp;gt;] do_syscall_64+0x35/0x80     [&amp;lt;000000008fc6fcde&amp;gt;] entry_SYSCALL_64_after_hwframe+0x46/0xb0 The reason is that the vkms_init() returns without checking the return value of vkms_create(), and if the vkms_create() failed, the config allocated at the beginning of vkms_init() is leaked.  vkms_init()    config = kmalloc(...) # config allocated    ...    return vkms_create() # vkms_create failed and config is leaked Fix this problem by checking return value of vkms_create() and free the config if error happened.&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 106 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/vkms: Fix memory leak in vkms_init() A memory leak was reported after the vkms module install failed. unreferenced object 0xffff88810bc28520 (size 16):   comm &amp;#34;modprobe&amp;#34;, pid 9662, jiffies 4298009455 (age 42.590s)   hex dump (first 16 bytes):     01 01 00 64 81 88 ff ff 00 00 dc 0a 81 88 ff ff  ...d............   backtrace:     [&amp;lt;00000000e7561ff8&amp;gt;] kmalloc_trace+0x27/0x60     [&amp;lt;000000000b1954a0&amp;gt;] 0xffffffffc45200a9     [&amp;lt;00000000abbf1da0&amp;gt;] do_one_initcall+0xd0/0x4f0     [&amp;lt;000000001505ee87&amp;gt;] do_init_module+0x1a4/0x680     [&amp;lt;00000000958079ad&amp;gt;] load_module+0x6249/0x7110     [&amp;lt;00000000117e4696&amp;gt;] __do_sys_finit_module+0x140/0x200     [&amp;lt;00000000f74b12d2&amp;gt;] do_syscall_64+0x35/0x80     [&amp;lt;000000008fc6fcde&amp;gt;] entry_SYSCALL_64_after_hwframe+0x46/0xb0 The reason is that the vkms_init() returns without checking the return value of vkms_create(), and if the vkms_create() failed, the config allocated at the beginning of vkms_init() is leaked.  vkms_init()    config = kmalloc(...) # config allocated    ...    return vkms_create() # vkms_create failed and config is leaked Fix this problem by checking return value of vkms_create() and free the config if error happened.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2022-50269</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2053 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2025-2053</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher beschriebene Auswirkungen zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher beschriebene Auswirkungen zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2025-2053</guid>
    </item>
  </channel>
</rss>
