<?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 16:50:16 +0000</lastBuildDate>
    <item>
      <title>ALSA-2026:93413 — Important: kernel security, bug fix, and enhancement update</title>
      <link>https://127.0.0.1:10001/vuln/alsa-2026:93413</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:10: kernel-abi-stablelists, AlmaLinux:10: kernel-doc&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: Kernel: Denial of Service in network socket error handling (CVE-2026-22977)
  * kernel: x86/CPU/AMD: Prevent improper isolation of shared resources in Zen2&amp;#39;s op cache (CVE-2026-46174)
  * kernel: i2c: stub: Reject I2C block transfers with invalid length (CVE-2026-64191)
  * kernel: Linux kernel: PPP over L2TP Use-After-Free vulnerability (CVE-2026-68398)
  * kernel: mptcp: pm: userspace: fix use-after-free in get_local_id (CVE-2026-68169)
  * kernel: tipc: require net admin for TIPCv2 netlink mutators (CVE-2026-74283)
  * kernel: mptcp: options: reset DSS fields in case of unexpected size (CVE-2026-80586)
  * kernel: entry: Fix seccomp bypass after ptrace with TSYNC (CVE-2026-89603)
  * kernel: KVM: nVMX: Always flush vpid02 on first use (CVE-2026-89932)
  * kernel: scsi: target: iscsi: Reserve a terminator byte for the login payload (CVE-2026-90011)
  * kernel: virtio-fs: avoid double-free on failed queue setup (CVE-2026-93827)
  * kernel: smb: client: bound dirent name against end of SMB response in cifs_filldir (CVE-2026-93787)
  * kernel: KEYS: encrypted: fix integer overflow of datablob_len (CVE-2026-98222)
  * kernel: xfrm: hold net_device reference under RCU in bundle creation (CVE-2026-98364)
  * kernel: ipv4: free inet_opt and ireq_opt after an RCU grace period (CVE-2026-98432)
  * kernel: nvmet-auth: fix out-of-bounds write in nvmet_auth_challen…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:10: kernel-abi-stablelists, AlmaLinux:10: kernel-doc&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: Kernel: Denial of Service in network socket error handling (CVE-2026-22977)
  * kernel: x86/CPU/AMD: Prevent improper isolation of shared resources in Zen2&amp;#39;s op cache (CVE-2026-46174)
  * kernel: i2c: stub: Reject I2C block transfers with invalid length (CVE-2026-64191)
  * kernel: Linux kernel: PPP over L2TP Use-After-Free vulnerability (CVE-2026-68398)
  * kernel: mptcp: pm: userspace: fix use-after-free in get_local_id (CVE-2026-68169)
  * kernel: tipc: require net admin for TIPCv2 netlink mutators (CVE-2026-74283)
  * kernel: mptcp: options: reset DSS fields in case of unexpected size (CVE-2026-80586)
  * kernel: entry: Fix seccomp bypass after ptrace with TSYNC (CVE-2026-89603)
  * kernel: KVM: nVMX: Always flush vpid02 on first use (CVE-2026-89932)
  * kernel: scsi: target: iscsi: Reserve a terminator byte for the login payload (CVE-2026-90011)
  * kernel: virtio-fs: avoid double-free on failed queue setup (CVE-2026-93827)
  * kernel: smb: client: bound dirent name against end of SMB response in cifs_filldir (CVE-2026-93787)
  * kernel: KEYS: encrypted: fix integer overflow of datablob_len (CVE-2026-98222)
  * kernel: xfrm: hold net_device reference under RCU in bundle creation (CVE-2026-98364)
  * kernel: ipv4: free inet_opt and ireq_opt after an RCU grace period (CVE-2026-98432)
  * kernel: nvmet-auth: fix out-of-bounds write in nvmet_auth_challen…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/alsa-2026:93413</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-89932</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-89932</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-89932</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1253 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-1253</link>
      <description>certfr-2026-avi-1253</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-1253</guid>
    </item>
    <item>
      <title>OESA-2026-4357 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2026-4357</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:&lt;/p&gt;
&lt;p&gt;fs/ntfs3: reject index allocation if $BITMAP is empty but blocks exist&lt;/p&gt;
&lt;p&gt;Index allocation requires at least one bit in the $BITMAP attribute to
track usage of index entries. If the bitmap is empty while index blocks
are already present, this reflects on-disk corruption.&lt;/p&gt;
&lt;p&gt;syzbot triggered this condition using a malformed NTFS image. During a
rename() operation involving a long filename (which spans multiple
index entries), the empty bitmap allowed the name to be added without
valid tracking. Subsequent deletion of the original entry failed with
-ENOENT, due to unexpected index state.&lt;/p&gt;
&lt;p&gt;Reject such cases by verifying that the bitmap is not empty when index
blocks exist.(CVE-2025-40067)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;batman-adv: fix fragment reassembly length accounting&lt;/p&gt;
&lt;p&gt;batman-adv keeps a running payload length for queued fragments and uses it
to validate a fragment chain before reassembly.&lt;/p&gt;
&lt;p&gt;That accounting currently allows the accumulated fragment length to be
truncated during updates. As a result, malformed fragment chains can
bypass the intended validation and drive reassembly with inconsistent
length state, leading to a local denial of service.&lt;/p&gt;
&lt;p&gt;Fix the accounting by storing the accumulated length in a length-typed
field and rejecting update overflows before the existing validation logic
runs.&lt;/p&gt;
&lt;p&gt;T…&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:&lt;/p&gt;
&lt;p&gt;fs/ntfs3: reject index allocation if $BITMAP is empty but blocks exist&lt;/p&gt;
&lt;p&gt;Index allocation requires at least one bit in the $BITMAP attribute to
track usage of index entries. If the bitmap is empty while index blocks
are already present, this reflects on-disk corruption.&lt;/p&gt;
&lt;p&gt;syzbot triggered this condition using a malformed NTFS image. During a
rename() operation involving a long filename (which spans multiple
index entries), the empty bitmap allowed the name to be added without
valid tracking. Subsequent deletion of the original entry failed with
-ENOENT, due to unexpected index state.&lt;/p&gt;
&lt;p&gt;Reject such cases by verifying that the bitmap is not empty when index
blocks exist.(CVE-2025-40067)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;batman-adv: fix fragment reassembly length accounting&lt;/p&gt;
&lt;p&gt;batman-adv keeps a running payload length for queued fragments and uses it
to validate a fragment chain before reassembly.&lt;/p&gt;
&lt;p&gt;That accounting currently allows the accumulated fragment length to be
truncated during updates. As a result, malformed fragment chains can
bypass the intended validation and drive reassembly with inconsistent
length state, leading to a local denial of service.&lt;/p&gt;
&lt;p&gt;Fix the accounting by storing the accumulated length in a length-typed
field and rejecting update overflows before the existing validation logic
runs.&lt;/p&gt;
&lt;p&gt;T…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2026-4357</guid>
    </item>
    <item>
      <title>RLSA-2026:93413 — Important: kernel security, bug fix, and enhancement update</title>
      <link>https://127.0.0.1:10001/vuln/rlsa-2026:93413</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:10: kernel, Rocky Linux:10: kernel-tools-debuginfo, Rocky Linux:10: kernel-64k-modules, Rocky Linux:10: kernel-debug-modules-extra, Rocky Linux:10: kernel-64k-debug-devel-matched, Rocky Linux:10: kernel-rt, Rocky Linux:10: kernel-rt-64k-modules, Rocky Linux:10: kernel-64k, Rocky Linux:10: kernel-64k-devel-matched, Rocky Linux:10: kernel-rt-64k-debug and 80 more&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: Kernel: Denial of Service in network socket error handling (CVE-2026-22977)&lt;/p&gt;
&lt;p&gt;* kernel: x86/CPU/AMD: Prevent improper isolation of shared resources in Zen2&amp;#39;s op cache (CVE-2026-46174)&lt;/p&gt;
&lt;p&gt;* kernel: i2c: stub: Reject I2C block transfers with invalid length (CVE-2026-64191)&lt;/p&gt;
&lt;p&gt;* kernel: Linux kernel: PPP over L2TP Use-After-Free vulnerability (CVE-2026-68398)&lt;/p&gt;
&lt;p&gt;* kernel: mptcp: pm: userspace: fix use-after-free in get_local_id (CVE-2026-68169)&lt;/p&gt;
&lt;p&gt;* kernel: tipc: require net admin for TIPCv2 netlink mutators (CVE-2026-74283)&lt;/p&gt;
&lt;p&gt;* kernel: mptcp: options: reset DSS fields in case of unexpected size (CVE-2026-80586)&lt;/p&gt;
&lt;p&gt;* kernel: entry: Fix seccomp bypass after ptrace with TSYNC (CVE-2026-89603)&lt;/p&gt;
&lt;p&gt;* kernel: KVM: nVMX: Always flush vpid02 on first use (CVE-2026-89932)&lt;/p&gt;
&lt;p&gt;* kernel: scsi: target: iscsi: Reserve a terminator byte for the login payload (CVE-2026-90011)&lt;/p&gt;
&lt;p&gt;* kernel: virtio-fs: avoid double-free on failed queue setup (CVE-2026-93827)&lt;/p&gt;
&lt;p&gt;* kernel: smb: client: bound dirent name against end of SMB response in cifs_filldir (CVE-2026-93787)&lt;/p&gt;
&lt;p&gt;* kernel: KEYS: encrypted: fix integer overflow of datablob_len (CVE-2026-98222)&lt;/p&gt;
&lt;p&gt;* kernel: xfrm: hold net_device reference under RCU in bundle creation (CVE-2026-98364)&lt;/p&gt;
&lt;p&gt;* kernel: ipv4: free inet_opt and ireq_opt after an RCU grace period (CVE-2026-98432)&lt;/p&gt;
&lt;p&gt;* kernel: nvmet-auth: fix out-of-bounds write in nvmet_auth_challenge() (CVE-2026-98725)…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:10: kernel, Rocky Linux:10: kernel-tools-debuginfo, Rocky Linux:10: kernel-64k-modules, Rocky Linux:10: kernel-debug-modules-extra, Rocky Linux:10: kernel-64k-debug-devel-matched, Rocky Linux:10: kernel-rt, Rocky Linux:10: kernel-rt-64k-modules, Rocky Linux:10: kernel-64k, Rocky Linux:10: kernel-64k-devel-matched, Rocky Linux:10: kernel-rt-64k-debug and 80 more&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: Kernel: Denial of Service in network socket error handling (CVE-2026-22977)&lt;/p&gt;
&lt;p&gt;* kernel: x86/CPU/AMD: Prevent improper isolation of shared resources in Zen2&amp;#39;s op cache (CVE-2026-46174)&lt;/p&gt;
&lt;p&gt;* kernel: i2c: stub: Reject I2C block transfers with invalid length (CVE-2026-64191)&lt;/p&gt;
&lt;p&gt;* kernel: Linux kernel: PPP over L2TP Use-After-Free vulnerability (CVE-2026-68398)&lt;/p&gt;
&lt;p&gt;* kernel: mptcp: pm: userspace: fix use-after-free in get_local_id (CVE-2026-68169)&lt;/p&gt;
&lt;p&gt;* kernel: tipc: require net admin for TIPCv2 netlink mutators (CVE-2026-74283)&lt;/p&gt;
&lt;p&gt;* kernel: mptcp: options: reset DSS fields in case of unexpected size (CVE-2026-80586)&lt;/p&gt;
&lt;p&gt;* kernel: entry: Fix seccomp bypass after ptrace with TSYNC (CVE-2026-89603)&lt;/p&gt;
&lt;p&gt;* kernel: KVM: nVMX: Always flush vpid02 on first use (CVE-2026-89932)&lt;/p&gt;
&lt;p&gt;* kernel: scsi: target: iscsi: Reserve a terminator byte for the login payload (CVE-2026-90011)&lt;/p&gt;
&lt;p&gt;* kernel: virtio-fs: avoid double-free on failed queue setup (CVE-2026-93827)&lt;/p&gt;
&lt;p&gt;* kernel: smb: client: bound dirent name against end of SMB response in cifs_filldir (CVE-2026-93787)&lt;/p&gt;
&lt;p&gt;* kernel: KEYS: encrypted: fix integer overflow of datablob_len (CVE-2026-98222)&lt;/p&gt;
&lt;p&gt;* kernel: xfrm: hold net_device reference under RCU in bundle creation (CVE-2026-98364)&lt;/p&gt;
&lt;p&gt;* kernel: ipv4: free inet_opt and ireq_opt after an RCU grace period (CVE-2026-98432)&lt;/p&gt;
&lt;p&gt;* kernel: nvmet-auth: fix out-of-bounds write in nvmet_auth_challenge() (CVE-2026-98725)…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/rlsa-2026:93413</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-89932</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-89932</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 247 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: KVM: nVMX: Always flush vpid02 on first use Make sure vpid02 is always flushed on first use by setting last_vpid=0 when allocating vpid02.  nested_vmx_transition_tlb_flush() will always detect a VPID change on first VM-Enter after VMXON, because VPID=0 in vmcs12 is not allowed if L1 enables VPID. This avoids using stale TLB entries from a previous lifetime of the VPID, that might have been associated with a different vCPU (or a completely different VM). Note that last_vpid is already being initialized as 0 when the vCPU is created, but it is not reset when vpid02 is freed on VMXOFF. Hence, the problem can only occur if L1 does VMXOFF -&amp;gt; VMXON, runs an L2, and KVM happens to reuse a VPID that has TLB entries on the physical CPU.&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 247 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: KVM: nVMX: Always flush vpid02 on first use Make sure vpid02 is always flushed on first use by setting last_vpid=0 when allocating vpid02.  nested_vmx_transition_tlb_flush() will always detect a VPID change on first VM-Enter after VMXON, because VPID=0 in vmcs12 is not allowed if L1 enables VPID. This avoids using stale TLB entries from a previous lifetime of the VPID, that might have been associated with a different vCPU (or a completely different VM). Note that last_vpid is already being initialized as 0 when the vCPU is created, but it is not reset when vpid02 is freed on VMXOFF. Hence, the problem can only occur if L1 does VMXOFF -&amp;gt; VMXON, runs an L2, and KVM happens to reuse a VPID that has TLB entries on the physical CPU.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-89932</guid>
    </item>
  </channel>
</rss>
