<?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://127.0.0.1:10001</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>Sat, 21 Nov 2026 12:43:51 +0000</lastBuildDate>
    <item>
      <title>ALSA-2026:87374 — Important: kernel-rt security update</title>
      <link>https://127.0.0.1:10001/vuln/alsa-2026:87374</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:8: kernel-rt, AlmaLinux:8: kernel-rt-core, AlmaLinux:8: kernel-rt-debug, AlmaLinux:8: kernel-rt-debug-core, AlmaLinux:8: kernel-rt-debug-devel, AlmaLinux:8: kernel-rt-debug-modules, AlmaLinux:8: kernel-rt-debug-modules-extra, AlmaLinux:8: kernel-rt-devel, AlmaLinux:8: kernel-rt-modules, AlmaLinux:8: kernel-rt-modules-extra&lt;/p&gt;
&lt;p&gt;The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: ipv4: raw: reject IP_HDRINCL packets with ihl &amp;lt; 5 (CVE-2026-64114)
  * kernel: fuse: re-lock request before returning from fuse_ref_folio() (CVE-2026-64266)
  * kernel: ipv4: fib: free fib_alias with kfree_rcu() on insert error path (CVE-2026-64572)
  * kernel: ALSA: seq: close a re-opened queue timer in the destructor (CVE-2026-68202)
  * kernel: xfs: bounds-check buffer log item&amp;#39;s dirty bitmap (CVE-2026-80536)
  * kernel: inet: frags: strip GSO state from fragments before reassembly (CVE-2026-80590)
  * kernel: vfio/pci: clear vdev-&amp;gt;msi_perm after freeing it on init failure (CVE-2026-89777)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:8: kernel-rt, AlmaLinux:8: kernel-rt-core, AlmaLinux:8: kernel-rt-debug, AlmaLinux:8: kernel-rt-debug-core, AlmaLinux:8: kernel-rt-debug-devel, AlmaLinux:8: kernel-rt-debug-modules, AlmaLinux:8: kernel-rt-debug-modules-extra, AlmaLinux:8: kernel-rt-devel, AlmaLinux:8: kernel-rt-modules, AlmaLinux:8: kernel-rt-modules-extra&lt;/p&gt;
&lt;p&gt;The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: ipv4: raw: reject IP_HDRINCL packets with ihl &amp;lt; 5 (CVE-2026-64114)
  * kernel: fuse: re-lock request before returning from fuse_ref_folio() (CVE-2026-64266)
  * kernel: ipv4: fib: free fib_alias with kfree_rcu() on insert error path (CVE-2026-64572)
  * kernel: ALSA: seq: close a re-opened queue timer in the destructor (CVE-2026-68202)
  * kernel: xfs: bounds-check buffer log item&amp;#39;s dirty bitmap (CVE-2026-80536)
  * kernel: inet: frags: strip GSO state from fragments before reassembly (CVE-2026-80590)
  * kernel: vfio/pci: clear vdev-&amp;gt;msi_perm after freeing it on init failure (CVE-2026-89777)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/alsa-2026:87374</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-80536</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-80536</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://127.0.0.1:10001/vuln/bell-cve-2026-80536</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1119 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-1119</link>
      <description>certfr-2026-avi-1119</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-1119</guid>
    </item>
    <item>
      <title>OESA-2026-3706 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2026-3706</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.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:net: af_can: do not leave a dangling sk pointer in can_create()On error can_create() frees the allocated sk object, but sock_init_data()has already attached it to the provided sock object. This will leave adangling sk pointer in the sock object and may cause use-after-free later.(CVE-2024-56603)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;hdlc_ppp: sync per-proto timers before freeing hdlc state&lt;/p&gt;
&lt;p&gt;Each PPP control protocol (LCP/IPCP/IPV6CP) embedded in struct ppp
registers a timer via timer_setup(). That struct ppp is the
hdlc-&amp;amp;gt;state allocation, which detach_hdlc_protocol() frees with kfree()
in both teardown paths: unregister_hdlc_device() and the re-attach inside
attach_hdlc_protocol().&lt;/p&gt;
&lt;p&gt;The ppp proto never registered a .detach callback, so
detach_hdlc_protocol() performs no timer synchronization before the
kfree(). The only cancel, timer_delete(&amp;amp;amp;proto-&amp;amp;gt;timer) in ppp_cp_event(),
is partial (it does not wait for a running callback) and only runs on the
-&amp;amp;gt;CLOSED transition; ppp_stop()/ppp_close() do not sync either. A
ppp_timer callback already executing (blocked on ppp-&amp;amp;gt;lock) survives the
kfree and then dereferences proto-&amp;amp;gt;state / ppp-&amp;amp;gt;lock in freed memory,
leading to a use-after-free.&lt;/p&gt;
&lt;p&gt;Fix this by adding a .detach helper that calls timer_shutdown_sync() on
every per-proto timer. detach_hd…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.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:net: af_can: do not leave a dangling sk pointer in can_create()On error can_create() frees the allocated sk object, but sock_init_data()has already attached it to the provided sock object. This will leave adangling sk pointer in the sock object and may cause use-after-free later.(CVE-2024-56603)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;hdlc_ppp: sync per-proto timers before freeing hdlc state&lt;/p&gt;
&lt;p&gt;Each PPP control protocol (LCP/IPCP/IPV6CP) embedded in struct ppp
registers a timer via timer_setup(). That struct ppp is the
hdlc-&amp;amp;gt;state allocation, which detach_hdlc_protocol() frees with kfree()
in both teardown paths: unregister_hdlc_device() and the re-attach inside
attach_hdlc_protocol().&lt;/p&gt;
&lt;p&gt;The ppp proto never registered a .detach callback, so
detach_hdlc_protocol() performs no timer synchronization before the
kfree(). The only cancel, timer_delete(&amp;amp;amp;proto-&amp;amp;gt;timer) in ppp_cp_event(),
is partial (it does not wait for a running callback) and only runs on the
-&amp;amp;gt;CLOSED transition; ppp_stop()/ppp_close() do not sync either. A
ppp_timer callback already executing (blocked on ppp-&amp;amp;gt;lock) survives the
kfree and then dereferences proto-&amp;amp;gt;state / ppp-&amp;amp;gt;lock in freed memory,
leading to a use-after-free.&lt;/p&gt;
&lt;p&gt;Fix this by adding a .detach helper that calls timer_shutdown_sync() on
every per-proto timer. detach_hd…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2026-3706</guid>
    </item>
    <item>
      <title>RLSA-2026:87374 — Important: kernel-rt security update</title>
      <link>https://127.0.0.1:10001/vuln/rlsa-2026:87374</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:8: kernel-rt, Rocky Linux:8: kernel-rt-core, Rocky Linux:8: kernel-rt-debug, Rocky Linux:8: kernel-rt-debug-core, Rocky Linux:8: kernel-rt-debug-debuginfo, Rocky Linux:8: kernel-rt-debug-devel, Rocky Linux:8: kernel-rt-debuginfo, Rocky Linux:8: kernel-rt-debuginfo-common-x86_64, Rocky Linux:8: kernel-rt-debug-kvm, Rocky Linux:8: kernel-rt-debug-modules and 5 more&lt;/p&gt;
&lt;p&gt;The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: ipv4: raw: reject IP_HDRINCL packets with ihl &amp;lt; 5 (CVE-2026-64114)&lt;/p&gt;
&lt;p&gt;* kernel: fuse: re-lock request before returning from fuse_ref_folio() (CVE-2026-64266)&lt;/p&gt;
&lt;p&gt;* kernel: ipv4: fib: free fib_alias with kfree_rcu() on insert error path (CVE-2026-64572)&lt;/p&gt;
&lt;p&gt;* kernel: ALSA: seq: close a re-opened queue timer in the destructor (CVE-2026-68202)&lt;/p&gt;
&lt;p&gt;* kernel: xfs: bounds-check buffer log item&amp;#39;s dirty bitmap (CVE-2026-80536)&lt;/p&gt;
&lt;p&gt;* kernel: inet: frags: strip GSO state from fragments before reassembly (CVE-2026-80590)&lt;/p&gt;
&lt;p&gt;* kernel: vfio/pci: clear vdev-&amp;gt;msi_perm after freeing it on init failure (CVE-2026-89777)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:8: kernel-rt, Rocky Linux:8: kernel-rt-core, Rocky Linux:8: kernel-rt-debug, Rocky Linux:8: kernel-rt-debug-core, Rocky Linux:8: kernel-rt-debug-debuginfo, Rocky Linux:8: kernel-rt-debug-devel, Rocky Linux:8: kernel-rt-debuginfo, Rocky Linux:8: kernel-rt-debuginfo-common-x86_64, Rocky Linux:8: kernel-rt-debug-kvm, Rocky Linux:8: kernel-rt-debug-modules and 5 more&lt;/p&gt;
&lt;p&gt;The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: ipv4: raw: reject IP_HDRINCL packets with ihl &amp;lt; 5 (CVE-2026-64114)&lt;/p&gt;
&lt;p&gt;* kernel: fuse: re-lock request before returning from fuse_ref_folio() (CVE-2026-64266)&lt;/p&gt;
&lt;p&gt;* kernel: ipv4: fib: free fib_alias with kfree_rcu() on insert error path (CVE-2026-64572)&lt;/p&gt;
&lt;p&gt;* kernel: ALSA: seq: close a re-opened queue timer in the destructor (CVE-2026-68202)&lt;/p&gt;
&lt;p&gt;* kernel: xfs: bounds-check buffer log item&amp;#39;s dirty bitmap (CVE-2026-80536)&lt;/p&gt;
&lt;p&gt;* kernel: inet: frags: strip GSO state from fragments before reassembly (CVE-2026-80590)&lt;/p&gt;
&lt;p&gt;* kernel: vfio/pci: clear vdev-&amp;gt;msi_perm after freeing it on init failure (CVE-2026-89777)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/rlsa-2026:87374</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-80536</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-80536</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, 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 and 248 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: xfs: bounds-check buffer log item&amp;#39;s dirty bitmap xlog_recover_do_reg_buffer() replays each dirty region described by a buffer log item&amp;#39;s bitmap into the buffer read for that item: 	memcpy(xfs_buf_offset(bp, (uint)bit &amp;lt;&amp;lt; XFS_BLF_SHIFT), 		item-&amp;gt;ri_buf[i].iov_base, 		nbits &amp;lt;&amp;lt; XFS_BLF_SHIFT); The destination offset (bit/nbits, from the logged dirty bitmap) and the buffer size (from the logged blf_len) are both attacker-controlled and otherwise unrelated, yet the only thing bounding the copy is an ASSERT(), which compiles away on production kernels. A crafted image logging a small blf_len together with a bitmap bit past the end of that buffer drives the memcpy() past the buffer&amp;#39;s allocation, corrupting adjacent kernel heap during mount-time log recovery. This is reachable by anyone who can get a crafted image mounted -- the malicious-filesystem threat model XFS already guards against elsewhere. Turn the ASSERT() into a real XFS_IS_CORRUPT() check that aborts recovery of the buffer with -EFSCORRUPTED, consistent with the validate-and-fail idiom already used in xlog_recover_do_inode_buffer() and xfs_dquot_item_recover.c. xlog_recover_do_reg_buffer() therefore becomes STATIC int and its three callers propagate the error. Found and confirmed with KASAN on a CONFIG_XFS_DEBUG=n build: the crafted image trips a slab-out-of-bounds write before this change and fails recovery cleanly with -EFSCORRUPTED after it.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, 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 and 248 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: xfs: bounds-check buffer log item&amp;#39;s dirty bitmap xlog_recover_do_reg_buffer() replays each dirty region described by a buffer log item&amp;#39;s bitmap into the buffer read for that item: 	memcpy(xfs_buf_offset(bp, (uint)bit &amp;lt;&amp;lt; XFS_BLF_SHIFT), 		item-&amp;gt;ri_buf[i].iov_base, 		nbits &amp;lt;&amp;lt; XFS_BLF_SHIFT); The destination offset (bit/nbits, from the logged dirty bitmap) and the buffer size (from the logged blf_len) are both attacker-controlled and otherwise unrelated, yet the only thing bounding the copy is an ASSERT(), which compiles away on production kernels. A crafted image logging a small blf_len together with a bitmap bit past the end of that buffer drives the memcpy() past the buffer&amp;#39;s allocation, corrupting adjacent kernel heap during mount-time log recovery. This is reachable by anyone who can get a crafted image mounted -- the malicious-filesystem threat model XFS already guards against elsewhere. Turn the ASSERT() into a real XFS_IS_CORRUPT() check that aborts recovery of the buffer with -EFSCORRUPTED, consistent with the validate-and-fail idiom already used in xlog_recover_do_inode_buffer() and xfs_dquot_item_recover.c. xlog_recover_do_reg_buffer() therefore becomes STATIC int and its three callers propagate the error. Found and confirmed with KASAN on a CONFIG_XFS_DEBUG=n build: the crafted image trips a slab-out-of-bounds write before this change and fails recovery cleanly with -EFSCORRUPTED after it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-80536</guid>
    </item>
  </channel>
</rss>
