<?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:41 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-04560</title>
      <link>https://db.gcve.eu/vuln/bdu:2026-04560</link>
      <description>bdu:2026-04560</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/bdu:2026-04560</guid>
    </item>
    <item>
      <title>fkie_cve-2022-50004</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2022-50004</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;xfrm: policy: fix metadata dst-&amp;gt;dev xmit null pointer dereference&lt;/p&gt;
&lt;p&gt;When we try to transmit an skb with metadata_dst attached (i.e. dst-&amp;gt;dev
== NULL) through xfrm interface we can hit a null pointer dereference[1]
in xfrmi_xmit2() -&amp;gt; xfrm_lookup_with_ifid() due to the check for a
loopback skb device when there&amp;#39;s no policy which dereferences dst-&amp;gt;dev
unconditionally. Not having dst-&amp;gt;dev can be interepreted as it not being
a loopback device, so just add a check for a null dst_orig-&amp;gt;dev.&lt;/p&gt;
&lt;p&gt;With this fix xfrm interface&amp;#39;s Tx error counters go up as usual.&lt;/p&gt;
&lt;p&gt;[1] net-next calltrace captured via netconsole:
  BUG: kernel NULL pointer dereference, address: 00000000000000c0
  #PF: supervisor read access in kernel mode
  #PF: error_code(0x0000) - not-present page
  PGD 0 P4D 0
  Oops: 0000 [#1] PREEMPT SMP
  CPU: 1 PID: 7231 Comm: ping Kdump: loaded Not tainted 5.19.0+ #24
  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.0-1.fc36 04/01/2014
  RIP: 0010:xfrm_lookup_with_ifid+0x5eb/0xa60
  Code: 8d 74 24 38 e8 26 a4 37 00 48 89 c1 e9 12 fc ff ff 49 63 ed 41 83 fd be 0f 85 be 01 00 00 41 be ff ff ff ff 45 31 ed 48 8b 03 &amp;lt;f6&amp;gt; 80 c0 00 00 00 08 75 0f 41 80 bc 24 19 0d 00 00 01 0f 84 1e 02
  RSP: 0018:ffffb0db82c679f0 EFLAGS: 00010246
  RAX: 0000000000000000 RBX: ffffd0db7fcad430 RCX: ffffb0db82c67a10
  RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffb0db82c67a80
  RBP: ffffb0db82c67a80 R08: ffffb0db82c67a1…&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;xfrm: policy: fix metadata dst-&amp;gt;dev xmit null pointer dereference&lt;/p&gt;
&lt;p&gt;When we try to transmit an skb with metadata_dst attached (i.e. dst-&amp;gt;dev
== NULL) through xfrm interface we can hit a null pointer dereference[1]
in xfrmi_xmit2() -&amp;gt; xfrm_lookup_with_ifid() due to the check for a
loopback skb device when there&amp;#39;s no policy which dereferences dst-&amp;gt;dev
unconditionally. Not having dst-&amp;gt;dev can be interepreted as it not being
a loopback device, so just add a check for a null dst_orig-&amp;gt;dev.&lt;/p&gt;
&lt;p&gt;With this fix xfrm interface&amp;#39;s Tx error counters go up as usual.&lt;/p&gt;
&lt;p&gt;[1] net-next calltrace captured via netconsole:
  BUG: kernel NULL pointer dereference, address: 00000000000000c0
  #PF: supervisor read access in kernel mode
  #PF: error_code(0x0000) - not-present page
  PGD 0 P4D 0
  Oops: 0000 [#1] PREEMPT SMP
  CPU: 1 PID: 7231 Comm: ping Kdump: loaded Not tainted 5.19.0+ #24
  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.0-1.fc36 04/01/2014
  RIP: 0010:xfrm_lookup_with_ifid+0x5eb/0xa60
  Code: 8d 74 24 38 e8 26 a4 37 00 48 89 c1 e9 12 fc ff ff 49 63 ed 41 83 fd be 0f 85 be 01 00 00 41 be ff ff ff ff 45 31 ed 48 8b 03 &amp;lt;f6&amp;gt; 80 c0 00 00 00 08 75 0f 41 80 bc 24 19 0d 00 00 01 0f 84 1e 02
  RSP: 0018:ffffb0db82c679f0 EFLAGS: 00010246
  RAX: 0000000000000000 RBX: ffffd0db7fcad430 RCX: ffffb0db82c67a10
  RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffb0db82c67a80
  RBP: ffffb0db82c67a80 R08: ffffb0db82c67a1…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2022-50004</guid>
    </item>
    <item>
      <title>GHSA-mpjj-88pq-258q</title>
      <link>https://db.gcve.eu/vuln/ghsa-mpjj-88pq-258q</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;xfrm: policy: fix metadata dst-&amp;gt;dev xmit null pointer dereference&lt;/p&gt;
&lt;p&gt;When we try to transmit an skb with metadata_dst attached (i.e. dst-&amp;gt;dev
== NULL) through xfrm interface we can hit a null pointer dereference[1]
in xfrmi_xmit2() -&amp;gt; xfrm_lookup_with_ifid() due to the check for a
loopback skb device when there&amp;#39;s no policy which dereferences dst-&amp;gt;dev
unconditionally. Not having dst-&amp;gt;dev can be interepreted as it not being
a loopback device, so just add a check for a null dst_orig-&amp;gt;dev.&lt;/p&gt;
&lt;p&gt;With this fix xfrm interface&amp;#39;s Tx error counters go up as usual.&lt;/p&gt;
&lt;p&gt;[1] net-next calltrace captured via netconsole:
  BUG: kernel NULL pointer dereference, address: 00000000000000c0
  #PF: supervisor read access in kernel mode
  #PF: error_code(0x0000) - not-present page
  PGD 0 P4D 0
  Oops: 0000 [#1] PREEMPT SMP
  CPU: 1 PID: 7231 Comm: ping Kdump: loaded Not tainted 5.19.0+ #24
  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.0-1.fc36 04/01/2014
  RIP: 0010:xfrm_lookup_with_ifid+0x5eb/0xa60
  Code: 8d 74 24 38 e8 26 a4 37 00 48 89 c1 e9 12 fc ff ff 49 63 ed 41 83 fd be 0f 85 be 01 00 00 41 be ff ff ff ff 45 31 ed 48 8b 03 &amp;lt;f6&amp;gt; 80 c0 00 00 00 08 75 0f 41 80 bc 24 19 0d 00 00 01 0f 84 1e 02
  RSP: 0018:ffffb0db82c679f0 EFLAGS: 00010246
  RAX: 0000000000000000 RBX: ffffd0db7fcad430 RCX: ffffb0db82c67a10
  RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffb0db82c67a80
  RBP: ffffb0db82c67a80 R08: ffffb0db82c67a1…&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;xfrm: policy: fix metadata dst-&amp;gt;dev xmit null pointer dereference&lt;/p&gt;
&lt;p&gt;When we try to transmit an skb with metadata_dst attached (i.e. dst-&amp;gt;dev
== NULL) through xfrm interface we can hit a null pointer dereference[1]
in xfrmi_xmit2() -&amp;gt; xfrm_lookup_with_ifid() due to the check for a
loopback skb device when there&amp;#39;s no policy which dereferences dst-&amp;gt;dev
unconditionally. Not having dst-&amp;gt;dev can be interepreted as it not being
a loopback device, so just add a check for a null dst_orig-&amp;gt;dev.&lt;/p&gt;
&lt;p&gt;With this fix xfrm interface&amp;#39;s Tx error counters go up as usual.&lt;/p&gt;
&lt;p&gt;[1] net-next calltrace captured via netconsole:
  BUG: kernel NULL pointer dereference, address: 00000000000000c0
  #PF: supervisor read access in kernel mode
  #PF: error_code(0x0000) - not-present page
  PGD 0 P4D 0
  Oops: 0000 [#1] PREEMPT SMP
  CPU: 1 PID: 7231 Comm: ping Kdump: loaded Not tainted 5.19.0+ #24
  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.0-1.fc36 04/01/2014
  RIP: 0010:xfrm_lookup_with_ifid+0x5eb/0xa60
  Code: 8d 74 24 38 e8 26 a4 37 00 48 89 c1 e9 12 fc ff ff 49 63 ed 41 83 fd be 0f 85 be 01 00 00 41 be ff ff ff ff 45 31 ed 48 8b 03 &amp;lt;f6&amp;gt; 80 c0 00 00 00 08 75 0f 41 80 bc 24 19 0d 00 00 01 0f 84 1e 02
  RSP: 0018:ffffb0db82c679f0 EFLAGS: 00010246
  RAX: 0000000000000000 RBX: ffffd0db7fcad430 RCX: ffffb0db82c67a10
  RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffb0db82c67a80
  RBP: ffffb0db82c67a80 R08: ffffb0db82c67a1…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-mpjj-88pq-258q</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-50004</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2022-50004</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 94 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: xfrm: policy: fix metadata dst-&amp;gt;dev xmit null pointer dereference When we try to transmit an skb with metadata_dst attached (i.e. dst-&amp;gt;dev == NULL) through xfrm interface we can hit a null pointer dereference[1] in xfrmi_xmit2() -&amp;gt; xfrm_lookup_with_ifid() due to the check for a loopback skb device when there&amp;#39;s no policy which dereferences dst-&amp;gt;dev unconditionally. Not having dst-&amp;gt;dev can be interepreted as it not being a loopback device, so just add a check for a null dst_orig-&amp;gt;dev. With this fix xfrm interface&amp;#39;s Tx error counters go up as usual. [1] net-next calltrace captured via netconsole:   BUG: kernel NULL pointer dereference, address: 00000000000000c0   #PF: supervisor read access in kernel mode   #PF: error_code(0x0000) - not-present page   PGD 0 P4D 0   Oops: 0000 [#1] PREEMPT SMP   CPU: 1 PID: 7231 Comm: ping Kdump: loaded Not tainted 5.19.0+ #24   Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.0-1.fc36 04/01/2014   RIP: 0010:xfrm_lookup_with_ifid+0x5eb/0xa60   Code: 8d 74 24 38 e8 26 a4 37 00 48 89 c1 e9 12 fc ff ff 49 63 ed 41 83 fd be 0f 85 be 01 00 00 41 be ff ff ff ff 45 31 ed 48 8b 03 &amp;lt;f6&amp;gt; 80 c0 00 00 00 08 75 0f 41 80 bc 24 19 0d 00 00 01 0f 84 1e 02   RSP: 0018:ffffb0db82c679f0 EFLAGS: 00010246   RAX: 0000000000000000 RBX: ffffd0db7fcad430 RCX: ffffb0db82c67a10   RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffb0db82c67a80   RBP: ffffb0db82c67a80 R08: ffffb0db82c67a14 R0…&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 94 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: xfrm: policy: fix metadata dst-&amp;gt;dev xmit null pointer dereference When we try to transmit an skb with metadata_dst attached (i.e. dst-&amp;gt;dev == NULL) through xfrm interface we can hit a null pointer dereference[1] in xfrmi_xmit2() -&amp;gt; xfrm_lookup_with_ifid() due to the check for a loopback skb device when there&amp;#39;s no policy which dereferences dst-&amp;gt;dev unconditionally. Not having dst-&amp;gt;dev can be interepreted as it not being a loopback device, so just add a check for a null dst_orig-&amp;gt;dev. With this fix xfrm interface&amp;#39;s Tx error counters go up as usual. [1] net-next calltrace captured via netconsole:   BUG: kernel NULL pointer dereference, address: 00000000000000c0   #PF: supervisor read access in kernel mode   #PF: error_code(0x0000) - not-present page   PGD 0 P4D 0   Oops: 0000 [#1] PREEMPT SMP   CPU: 1 PID: 7231 Comm: ping Kdump: loaded Not tainted 5.19.0+ #24   Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.0-1.fc36 04/01/2014   RIP: 0010:xfrm_lookup_with_ifid+0x5eb/0xa60   Code: 8d 74 24 38 e8 26 a4 37 00 48 89 c1 e9 12 fc ff ff 49 63 ed 41 83 fd be 0f 85 be 01 00 00 41 be ff ff ff ff 45 31 ed 48 8b 03 &amp;lt;f6&amp;gt; 80 c0 00 00 00 08 75 0f 41 80 bc 24 19 0d 00 00 01 0f 84 1e 02   RSP: 0018:ffffb0db82c679f0 EFLAGS: 00010246   RAX: 0000000000000000 RBX: ffffd0db7fcad430 RCX: ffffb0db82c67a10   RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffb0db82c67a80   RBP: ffffb0db82c67a80 R08: ffffb0db82c67a14 R0…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2022-50004</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-1350 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2025-1350</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2025-1350</guid>
    </item>
  </channel>
</rss>
