<?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>Sun, 01 Nov 2026 22:00:06 +0000</lastBuildDate>
    <item>
      <title>certfr-2026-avi-1375 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
      <link>https://db.gcve.eu/vuln/certfr-2026-avi-1375</link>
      <description>certfr-2026-avi-1375</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/certfr-2026-avi-1375</guid>
    </item>
    <item>
      <title>fkie_cve-2026-98812</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-98812</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/mctp: publish the mctp_dev only after it is initialised&lt;/p&gt;
&lt;p&gt;mctp_add_dev() links the new mctp_dev into dev-&amp;gt;mctp_ptr before mdev-&amp;gt;dev
is assigned, so a reader that picks the device up in that window
dereferences a net_device pointer that is still NULL:&lt;/p&gt;
&lt;p&gt;KASAN: null-ptr-deref in range [0x00000000000000b0-0x00000000000000b7]
Call Trace:
 &amp;lt;TASK&amp;gt;
 ? __pfx_mctp_sendmsg (./include/linux/sockptr.h:49)
 ? __pfx_mctp_dst_output (net/mctp/route.c:41)
 ? selinux_socket_sendmsg (security/selinux/hooks.c:5278)
 ____sys_sendmsg (net/socket.c:775 (discriminator 1) net/socket.c:790
 (discriminator 1) net/socket.c:2684 (discriminator 1))
 ? __pfx_____sys_sendmsg (net/socket.c:1131)
 ? __pfx_copy_msghdr_from_user (net/socket.c:2590)
 ? update_cfs_rq_load_avg (kernel/sched/fair.c:5478)
 ___sys_sendmsg (net/socket.c:2738)
 ? __pfx____sys_sendmsg (net/socket.c:2625)
 ? perf_event_task_tick (./include/linux/rcupdate.h:838)
 ? sched_tick (kernel/sched/core.c:5818)
 ? clockevents_program_event (kernel/time/clockevents.c:372)
 ? fdget (./include/linux/rcupdate.h:873 fs/file.c:1100)
 __sys_sendmsg (net/socket.c:2770)
 ? __pfx___sys_sendmsg (net/socket.c:2751)
 do_syscall_64 (arch/x86/entry/syscall_64.c:63)
 entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)
 &amp;lt;/TASK&amp;gt;&lt;/p&gt;
&lt;p&gt;Fix by publishing only once the object is fully initialised:
__mctp_dev_get() runs under rcu_read_lock() only and hands
this object to readers as soon as m…&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;net/mctp: publish the mctp_dev only after it is initialised&lt;/p&gt;
&lt;p&gt;mctp_add_dev() links the new mctp_dev into dev-&amp;gt;mctp_ptr before mdev-&amp;gt;dev
is assigned, so a reader that picks the device up in that window
dereferences a net_device pointer that is still NULL:&lt;/p&gt;
&lt;p&gt;KASAN: null-ptr-deref in range [0x00000000000000b0-0x00000000000000b7]
Call Trace:
 &amp;lt;TASK&amp;gt;
 ? __pfx_mctp_sendmsg (./include/linux/sockptr.h:49)
 ? __pfx_mctp_dst_output (net/mctp/route.c:41)
 ? selinux_socket_sendmsg (security/selinux/hooks.c:5278)
 ____sys_sendmsg (net/socket.c:775 (discriminator 1) net/socket.c:790
 (discriminator 1) net/socket.c:2684 (discriminator 1))
 ? __pfx_____sys_sendmsg (net/socket.c:1131)
 ? __pfx_copy_msghdr_from_user (net/socket.c:2590)
 ? update_cfs_rq_load_avg (kernel/sched/fair.c:5478)
 ___sys_sendmsg (net/socket.c:2738)
 ? __pfx____sys_sendmsg (net/socket.c:2625)
 ? perf_event_task_tick (./include/linux/rcupdate.h:838)
 ? sched_tick (kernel/sched/core.c:5818)
 ? clockevents_program_event (kernel/time/clockevents.c:372)
 ? fdget (./include/linux/rcupdate.h:873 fs/file.c:1100)
 __sys_sendmsg (net/socket.c:2770)
 ? __pfx___sys_sendmsg (net/socket.c:2751)
 do_syscall_64 (arch/x86/entry/syscall_64.c:63)
 entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)
 &amp;lt;/TASK&amp;gt;&lt;/p&gt;
&lt;p&gt;Fix by publishing only once the object is fully initialised:
__mctp_dev_get() runs under rcu_read_lock() only and hands
this object to readers as soon as m…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-98812</guid>
    </item>
    <item>
      <title>GHSA-737h-gm8x-wcgc</title>
      <link>https://db.gcve.eu/vuln/ghsa-737h-gm8x-wcgc</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/mctp: publish the mctp_dev only after it is initialised&lt;/p&gt;
&lt;p&gt;mctp_add_dev() links the new mctp_dev into dev-&amp;gt;mctp_ptr before mdev-&amp;gt;dev
is assigned, so a reader that picks the device up in that window
dereferences a net_device pointer that is still NULL:&lt;/p&gt;
&lt;p&gt;KASAN: null-ptr-deref in range [0x00000000000000b0-0x00000000000000b7]
Call Trace:
 &amp;lt;TASK&amp;gt;
 ? __pfx_mctp_sendmsg (./include/linux/sockptr.h:49)
 ? __pfx_mctp_dst_output (net/mctp/route.c:41)
 ? selinux_socket_sendmsg (security/selinux/hooks.c:5278)
 ____sys_sendmsg (net/socket.c:775 (discriminator 1) net/socket.c:790
 (discriminator 1) net/socket.c:2684 (discriminator 1))
 ? __pfx_____sys_sendmsg (net/socket.c:1131)
 ? __pfx_copy_msghdr_from_user (net/socket.c:2590)
 ? update_cfs_rq_load_avg (kernel/sched/fair.c:5478)
 ___sys_sendmsg (net/socket.c:2738)
 ? __pfx____sys_sendmsg (net/socket.c:2625)
 ? perf_event_task_tick (./include/linux/rcupdate.h:838)
 ? sched_tick (kernel/sched/core.c:5818)
 ? clockevents_program_event (kernel/time/clockevents.c:372)
 ? fdget (./include/linux/rcupdate.h:873 fs/file.c:1100)
 __sys_sendmsg (net/socket.c:2770)
 ? __pfx___sys_sendmsg (net/socket.c:2751)
 do_syscall_64 (arch/x86/entry/syscall_64.c:63)
 entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)
 &amp;lt;/TASK&amp;gt;&lt;/p&gt;
&lt;p&gt;Fix by publishing only once the object is fully initialised:
__mctp_dev_get() runs under rcu_read_lock() only and hands
this object to readers as soon as m…&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;net/mctp: publish the mctp_dev only after it is initialised&lt;/p&gt;
&lt;p&gt;mctp_add_dev() links the new mctp_dev into dev-&amp;gt;mctp_ptr before mdev-&amp;gt;dev
is assigned, so a reader that picks the device up in that window
dereferences a net_device pointer that is still NULL:&lt;/p&gt;
&lt;p&gt;KASAN: null-ptr-deref in range [0x00000000000000b0-0x00000000000000b7]
Call Trace:
 &amp;lt;TASK&amp;gt;
 ? __pfx_mctp_sendmsg (./include/linux/sockptr.h:49)
 ? __pfx_mctp_dst_output (net/mctp/route.c:41)
 ? selinux_socket_sendmsg (security/selinux/hooks.c:5278)
 ____sys_sendmsg (net/socket.c:775 (discriminator 1) net/socket.c:790
 (discriminator 1) net/socket.c:2684 (discriminator 1))
 ? __pfx_____sys_sendmsg (net/socket.c:1131)
 ? __pfx_copy_msghdr_from_user (net/socket.c:2590)
 ? update_cfs_rq_load_avg (kernel/sched/fair.c:5478)
 ___sys_sendmsg (net/socket.c:2738)
 ? __pfx____sys_sendmsg (net/socket.c:2625)
 ? perf_event_task_tick (./include/linux/rcupdate.h:838)
 ? sched_tick (kernel/sched/core.c:5818)
 ? clockevents_program_event (kernel/time/clockevents.c:372)
 ? fdget (./include/linux/rcupdate.h:873 fs/file.c:1100)
 __sys_sendmsg (net/socket.c:2770)
 ? __pfx___sys_sendmsg (net/socket.c:2751)
 do_syscall_64 (arch/x86/entry/syscall_64.c:63)
 entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)
 &amp;lt;/TASK&amp;gt;&lt;/p&gt;
&lt;p&gt;Fix by publishing only once the object is fully initialised:
__mctp_dev_get() runs under rcu_read_lock() only and hands
this object to readers as soon as m…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-737h-gm8x-wcgc</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-98812 — net/mctp: publish the mctp_dev only after it is initialised</title>
      <link>https://db.gcve.eu/vuln/msrc_cve-2026-98812</link>
      <description>msrc_CVE-2026-98812</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/msrc_cve-2026-98812</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98812</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2026-98812</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 193 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/mctp: publish the mctp_dev only after it is initialised mctp_add_dev() links the new mctp_dev into dev-&amp;gt;mctp_ptr before mdev-&amp;gt;dev is assigned, so a reader that picks the device up in that window dereferences a net_device pointer that is still NULL: KASAN: null-ptr-deref in range [0x00000000000000b0-0x00000000000000b7] Call Trace:  &amp;lt;TASK&amp;gt;  ? __pfx_mctp_sendmsg (./include/linux/sockptr.h:49)  ? __pfx_mctp_dst_output (net/mctp/route.c:41)  ? selinux_socket_sendmsg (security/selinux/hooks.c:5278)  ____sys_sendmsg (net/socket.c:775 (discriminator 1) net/socket.c:790  (discriminator 1) net/socket.c:2684 (discriminator 1))  ? __pfx_____sys_sendmsg (net/socket.c:1131)  ? __pfx_copy_msghdr_from_user (net/socket.c:2590)  ? update_cfs_rq_load_avg (kernel/sched/fair.c:5478)  ___sys_sendmsg (net/socket.c:2738)  ? __pfx____sys_sendmsg (net/socket.c:2625)  ? perf_event_task_tick (./include/linux/rcupdate.h:838)  ? sched_tick (kernel/sched/core.c:5818)  ? clockevents_program_event (kernel/time/clockevents.c:372)  ? fdget (./include/linux/rcupdate.h:873 fs/file.c:1100)  __sys_sendmsg (net/socket.c:2770)  ? __pfx___sys_sendmsg (net/socket.c:2751)  do_syscall_64 (arch/x86/entry/syscall_64.c:63)  entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)  &amp;lt;/TASK&amp;gt; Fix by publishing only once the object is fully initialised: __mctp_dev_get() runs under rcu_read_lock() only and hands this object to readers as soon as mctp_…&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 193 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/mctp: publish the mctp_dev only after it is initialised mctp_add_dev() links the new mctp_dev into dev-&amp;gt;mctp_ptr before mdev-&amp;gt;dev is assigned, so a reader that picks the device up in that window dereferences a net_device pointer that is still NULL: KASAN: null-ptr-deref in range [0x00000000000000b0-0x00000000000000b7] Call Trace:  &amp;lt;TASK&amp;gt;  ? __pfx_mctp_sendmsg (./include/linux/sockptr.h:49)  ? __pfx_mctp_dst_output (net/mctp/route.c:41)  ? selinux_socket_sendmsg (security/selinux/hooks.c:5278)  ____sys_sendmsg (net/socket.c:775 (discriminator 1) net/socket.c:790  (discriminator 1) net/socket.c:2684 (discriminator 1))  ? __pfx_____sys_sendmsg (net/socket.c:1131)  ? __pfx_copy_msghdr_from_user (net/socket.c:2590)  ? update_cfs_rq_load_avg (kernel/sched/fair.c:5478)  ___sys_sendmsg (net/socket.c:2738)  ? __pfx____sys_sendmsg (net/socket.c:2625)  ? perf_event_task_tick (./include/linux/rcupdate.h:838)  ? sched_tick (kernel/sched/core.c:5818)  ? clockevents_program_event (kernel/time/clockevents.c:372)  ? fdget (./include/linux/rcupdate.h:873 fs/file.c:1100)  __sys_sendmsg (net/socket.c:2770)  ? __pfx___sys_sendmsg (net/socket.c:2751)  do_syscall_64 (arch/x86/entry/syscall_64.c:63)  entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)  &amp;lt;/TASK&amp;gt; Fix by publishing only once the object is fully initialised: __mctp_dev_get() runs under rcu_read_lock() only and hands this object to readers as soon as mctp_…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2026-98812</guid>
    </item>
  </channel>
</rss>
