<?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://vulnerability.circl.lu</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>Thu, 01 Oct 2026 16:42:42 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-64378</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-64378</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bell-cve-2026-64378</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0982 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Elles permettent à un attaquant de p…</title>
      <link>https://vulnerability.circl.lu/vuln/certfr-2026-avi-0982</link>
      <description>certfr-2026-avi-0982</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/certfr-2026-avi-0982</guid>
    </item>
    <item>
      <title>fkie_cve-2026-64378</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-64378</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;writeback: fix race between cgroup_writeback_umount() and inode_switch_wbs()&lt;/p&gt;
&lt;p&gt;When a container exits, the following BUG_ON() is occasionally triggered:&lt;/p&gt;
&lt;p&gt;==================================================================
 VFS: Busy inodes after unmount of sdb (ext4)
 ------------[ cut here ]------------
 kernel BUG at fs/super.c:695!
 CPU: 3 PID: 6 Comm: containerd-shim Tainted: G OE K 6.6 #1
 pstate: 63400009 (nZCv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)
 pc : generic_shutdown_super+0xf0/0x100
 lr : generic_shutdown_super+0xf0/0x100
 Call trace:
  generic_shutdown_super+0xf0/0x100
  kill_block_super+0x20/0x48
  ext4_kill_sb+0x28/0x60
  deactivate_locked_super+0x54/0x130
  deactivate_super+0x84/0xa0
  cleanup_mnt+0xa4/0x140
  __cleanup_mnt+0x18/0x28
  task_work_run+0x78/0xe0
  do_notify_resume+0x204/0x240
==================================================================&lt;/p&gt;
&lt;p&gt;The root cause is a race between cgroup_writeback_umount() and
inode_switch_wbs()/cleanup_offline_cgwb(). There is a window between
inode_prepare_wbs_switch() returning true and the subsequent
wb_queue_isw() call. Following is the process that triggers the issue:&lt;/p&gt;
&lt;p&gt;CPU A (umount)           |          CPU B (writeback)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                                 inode_switch_wbs/cleanup_offline_cgwb
                                  atomic_inc(&amp;amp;isw_nr_in_flight)…&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;writeback: fix race between cgroup_writeback_umount() and inode_switch_wbs()&lt;/p&gt;
&lt;p&gt;When a container exits, the following BUG_ON() is occasionally triggered:&lt;/p&gt;
&lt;p&gt;==================================================================
 VFS: Busy inodes after unmount of sdb (ext4)
 ------------[ cut here ]------------
 kernel BUG at fs/super.c:695!
 CPU: 3 PID: 6 Comm: containerd-shim Tainted: G OE K 6.6 #1
 pstate: 63400009 (nZCv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)
 pc : generic_shutdown_super+0xf0/0x100
 lr : generic_shutdown_super+0xf0/0x100
 Call trace:
  generic_shutdown_super+0xf0/0x100
  kill_block_super+0x20/0x48
  ext4_kill_sb+0x28/0x60
  deactivate_locked_super+0x54/0x130
  deactivate_super+0x84/0xa0
  cleanup_mnt+0xa4/0x140
  __cleanup_mnt+0x18/0x28
  task_work_run+0x78/0xe0
  do_notify_resume+0x204/0x240
==================================================================&lt;/p&gt;
&lt;p&gt;The root cause is a race between cgroup_writeback_umount() and
inode_switch_wbs()/cleanup_offline_cgwb(). There is a window between
inode_prepare_wbs_switch() returning true and the subsequent
wb_queue_isw() call. Following is the process that triggers the issue:&lt;/p&gt;
&lt;p&gt;CPU A (umount)           |          CPU B (writeback)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                                 inode_switch_wbs/cleanup_offline_cgwb
                                  atomic_inc(&amp;amp;isw_nr_in_flight)…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-64378</guid>
    </item>
    <item>
      <title>GHSA-325c-m2q7-75hg</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-325c-m2q7-75hg</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;writeback: fix race between cgroup_writeback_umount() and inode_switch_wbs()&lt;/p&gt;
&lt;p&gt;When a container exits, the following BUG_ON() is occasionally triggered:&lt;/p&gt;
&lt;p&gt;==================================================================
 VFS: Busy inodes after unmount of sdb (ext4)
 ------------[ cut here ]------------
 kernel BUG at fs/super.c:695!
 CPU: 3 PID: 6 Comm: containerd-shim Tainted: G OE K 6.6 #1
 pstate: 63400009 (nZCv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)
 pc : generic_shutdown_super+0xf0/0x100
 lr : generic_shutdown_super+0xf0/0x100
 Call trace:
  generic_shutdown_super+0xf0/0x100
  kill_block_super+0x20/0x48
  ext4_kill_sb+0x28/0x60
  deactivate_locked_super+0x54/0x130
  deactivate_super+0x84/0xa0
  cleanup_mnt+0xa4/0x140
  __cleanup_mnt+0x18/0x28
  task_work_run+0x78/0xe0
  do_notify_resume+0x204/0x240
==================================================================&lt;/p&gt;
&lt;p&gt;The root cause is a race between cgroup_writeback_umount() and
inode_switch_wbs()/cleanup_offline_cgwb(). There is a window between
inode_prepare_wbs_switch() returning true and the subsequent
wb_queue_isw() call. Following is the process that triggers the issue:&lt;/p&gt;
&lt;p&gt;CPU A (umount)           |          CPU B (writeback)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                                 inode_switch_wbs/cleanup_offline_cgwb
                                  atomic_inc(&amp;amp;isw_nr_in_flight)…&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;writeback: fix race between cgroup_writeback_umount() and inode_switch_wbs()&lt;/p&gt;
&lt;p&gt;When a container exits, the following BUG_ON() is occasionally triggered:&lt;/p&gt;
&lt;p&gt;==================================================================
 VFS: Busy inodes after unmount of sdb (ext4)
 ------------[ cut here ]------------
 kernel BUG at fs/super.c:695!
 CPU: 3 PID: 6 Comm: containerd-shim Tainted: G OE K 6.6 #1
 pstate: 63400009 (nZCv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)
 pc : generic_shutdown_super+0xf0/0x100
 lr : generic_shutdown_super+0xf0/0x100
 Call trace:
  generic_shutdown_super+0xf0/0x100
  kill_block_super+0x20/0x48
  ext4_kill_sb+0x28/0x60
  deactivate_locked_super+0x54/0x130
  deactivate_super+0x84/0xa0
  cleanup_mnt+0xa4/0x140
  __cleanup_mnt+0x18/0x28
  task_work_run+0x78/0xe0
  do_notify_resume+0x204/0x240
==================================================================&lt;/p&gt;
&lt;p&gt;The root cause is a race between cgroup_writeback_umount() and
inode_switch_wbs()/cleanup_offline_cgwb(). There is a window between
inode_prepare_wbs_switch() returning true and the subsequent
wb_queue_isw() call. Following is the process that triggers the issue:&lt;/p&gt;
&lt;p&gt;CPU A (umount)           |          CPU B (writeback)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                                 inode_switch_wbs/cleanup_offline_cgwb
                                  atomic_inc(&amp;amp;isw_nr_in_flight)…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-325c-m2q7-75hg</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-64378 — writeback: fix race between cgroup_writeback_umount() and inode_switch_wbs()</title>
      <link>https://vulnerability.circl.lu/vuln/msrc_cve-2026-64378</link>
      <description>msrc_CVE-2026-64378</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/msrc_cve-2026-64378</guid>
    </item>
    <item>
      <title>OESA-2026-3302 — kernel security update</title>
      <link>https://vulnerability.circl.lu/vuln/oesa-2026-3302</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;inet: RAW sockets using IPPROTO_RAW MUST drop incoming ICMP&lt;/p&gt;
&lt;p&gt;Yizhou Zhao reported that simply having one RAW socket on protocol
IPPROTO_RAW (255) was dangerous.&lt;/p&gt;
&lt;p&gt;socket(AF_INET, SOCK_RAW, 255);&lt;/p&gt;
&lt;p&gt;A malicious incoming ICMP packet can set the protocol field to 255
and match this socket, leading to FNHE cache changes.&lt;/p&gt;
&lt;p&gt;inner = IP(src=&amp;amp;quot;192.168.2.1&amp;amp;quot;, dst=&amp;amp;quot;8.8.8.8&amp;amp;quot;, proto=255)/Raw(&amp;amp;quot;TEST&amp;amp;quot;)
pkt = IP(src=&amp;amp;quot;192.168.1.1&amp;amp;quot;, dst=&amp;amp;quot;192.168.2.1&amp;amp;quot;)/ICMP(type=3, code=4, nexthopmtu=576)/inner&lt;/p&gt;
&lt;p&gt;&amp;amp;quot;man 7 raw&amp;amp;quot; states:&lt;/p&gt;
&lt;p&gt;A protocol of IPPROTO_RAW implies enabled IP_HDRINCL and is able
  to send any IP protocol that is specified in the passed header.
  Receiving of all IP protocols via IPPROTO_RAW is not possible
  using raw sockets.&lt;/p&gt;
&lt;p&gt;Make sure we drop these malicious packets.(CVE-2026-46266)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfilter: xt_policy: fix strict mode inbound policy matching&lt;/p&gt;
&lt;p&gt;match_policy_in() walks sec_path entries from the last transform to the
first one, but strict policy matching needs to consume info-&amp;amp;gt;pol[] in
the same forward order as the rule layout.&lt;/p&gt;
&lt;p&gt;Derive the strict-match policy position from the number of transforms
already consumed so that multi-element inbound rules are matched
consistently.(CVE-2026-52920)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the follow…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;inet: RAW sockets using IPPROTO_RAW MUST drop incoming ICMP&lt;/p&gt;
&lt;p&gt;Yizhou Zhao reported that simply having one RAW socket on protocol
IPPROTO_RAW (255) was dangerous.&lt;/p&gt;
&lt;p&gt;socket(AF_INET, SOCK_RAW, 255);&lt;/p&gt;
&lt;p&gt;A malicious incoming ICMP packet can set the protocol field to 255
and match this socket, leading to FNHE cache changes.&lt;/p&gt;
&lt;p&gt;inner = IP(src=&amp;amp;quot;192.168.2.1&amp;amp;quot;, dst=&amp;amp;quot;8.8.8.8&amp;amp;quot;, proto=255)/Raw(&amp;amp;quot;TEST&amp;amp;quot;)
pkt = IP(src=&amp;amp;quot;192.168.1.1&amp;amp;quot;, dst=&amp;amp;quot;192.168.2.1&amp;amp;quot;)/ICMP(type=3, code=4, nexthopmtu=576)/inner&lt;/p&gt;
&lt;p&gt;&amp;amp;quot;man 7 raw&amp;amp;quot; states:&lt;/p&gt;
&lt;p&gt;A protocol of IPPROTO_RAW implies enabled IP_HDRINCL and is able
  to send any IP protocol that is specified in the passed header.
  Receiving of all IP protocols via IPPROTO_RAW is not possible
  using raw sockets.&lt;/p&gt;
&lt;p&gt;Make sure we drop these malicious packets.(CVE-2026-46266)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfilter: xt_policy: fix strict mode inbound policy matching&lt;/p&gt;
&lt;p&gt;match_policy_in() walks sec_path entries from the last transform to the
first one, but strict policy matching needs to consume info-&amp;amp;gt;pol[] in
the same forward order as the rule layout.&lt;/p&gt;
&lt;p&gt;Derive the strict-match policy position from the number of transforms
already consumed so that multi-element inbound rules are matched
consistently.(CVE-2026-52920)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the follow…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/oesa-2026-3302</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11476-1 — kernel-devel-7.1.7-1.1 on GA media</title>
      <link>https://vulnerability.circl.lu/vuln/opensuse-su-2026:11476-1</link>
      <description>&lt;p&gt;kernel-devel-7.1.7-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.1.7-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/opensuse-su-2026:11476-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:23477-1 — Security update for the Linux Kernel</title>
      <link>https://vulnerability.circl.lu/vuln/suse-su-2026:23477-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://vulnerability.circl.lu/vuln/suse-su-2026:23477-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-64378</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-64378</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge and 245 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: writeback: fix race between cgroup_writeback_umount() and inode_switch_wbs() When a container exits, the following BUG_ON() is occasionally triggered: ==================================================================  VFS: Busy inodes after unmount of sdb (ext4)  ------------[ cut here ]------------  kernel BUG at fs/super.c:695!  CPU: 3 PID: 6 Comm: containerd-shim Tainted: G OE K 6.6 #1  pstate: 63400009 (nZCv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)  pc : generic_shutdown_super+0xf0/0x100  lr : generic_shutdown_super+0xf0/0x100  Call trace:   generic_shutdown_super+0xf0/0x100   kill_block_super+0x20/0x48   ext4_kill_sb+0x28/0x60   deactivate_locked_super+0x54/0x130   deactivate_super+0x84/0xa0   cleanup_mnt+0xa4/0x140   __cleanup_mnt+0x18/0x28   task_work_run+0x78/0xe0   do_notify_resume+0x204/0x240 ================================================================== The root cause is a race between cgroup_writeback_umount() and inode_switch_wbs()/cleanup_offline_cgwb(). There is a window between inode_prepare_wbs_switch() returning true and the subsequent wb_queue_isw() call. Following is the process that triggers the issue:       CPU A (umount)           |          CPU B (writeback) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~                                  inode_switch_wbs/cleanup_offline_cgwb                                   atomic_inc(&amp;amp;isw_nr_in_flight)…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge and 245 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: writeback: fix race between cgroup_writeback_umount() and inode_switch_wbs() When a container exits, the following BUG_ON() is occasionally triggered: ==================================================================  VFS: Busy inodes after unmount of sdb (ext4)  ------------[ cut here ]------------  kernel BUG at fs/super.c:695!  CPU: 3 PID: 6 Comm: containerd-shim Tainted: G OE K 6.6 #1  pstate: 63400009 (nZCv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)  pc : generic_shutdown_super+0xf0/0x100  lr : generic_shutdown_super+0xf0/0x100  Call trace:   generic_shutdown_super+0xf0/0x100   kill_block_super+0x20/0x48   ext4_kill_sb+0x28/0x60   deactivate_locked_super+0x54/0x130   deactivate_super+0x84/0xa0   cleanup_mnt+0xa4/0x140   __cleanup_mnt+0x18/0x28   task_work_run+0x78/0xe0   do_notify_resume+0x204/0x240 ================================================================== The root cause is a race between cgroup_writeback_umount() and inode_switch_wbs()/cleanup_offline_cgwb(). There is a window between inode_prepare_wbs_switch() returning true and the subsequent wb_queue_isw() call. Following is the process that triggers the issue:       CPU A (umount)           |          CPU B (writeback) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~                                  inode_switch_wbs/cleanup_offline_cgwb                                   atomic_inc(&amp;amp;isw_nr_in_flight)…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-64378</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2527 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2527</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, dazu können DoS-Angriffe, die Offenlegung von Informationen, die Beschädigung des Speichers oder die Umgehung von Sicherheitsmaßnahmen gehören.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, dazu können DoS-Angriffe, die Offenlegung von Informationen, die Beschädigung des Speichers oder die Umgehung von Sicherheitsmaßnahmen gehören.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2527</guid>
    </item>
  </channel>
</rss>
