<?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 03:59:24 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-52953</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-52953</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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: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-52953</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0926 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-0926</link>
      <description>certfr-2026-avi-0926</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0926</guid>
    </item>
    <item>
      <title>OESA-2026-3454 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2026-3454</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: 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;xfs: remove xfs_attr_leaf_hasname&lt;/p&gt;
&lt;p&gt;The calling convention of xfs_attr_leaf_hasname() is problematic, because
it returns a NULL buffer when xfs_attr3_leaf_read fails, a valid buffer
when xfs_attr3_leaf_lookup_int returns -ENOATTR or -EEXIST, and a
non-NULL buffer pointer for an already released buffer when
xfs_attr3_leaf_lookup_int fails with other error values.&lt;/p&gt;
&lt;p&gt;Fix this by simply open coding xfs_attr_leaf_hasname in the callers, so
that the buffer release code is done by each caller of
xfs_attr3_leaf_read.(CVE-2026-43153)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;x86/kexec: Disable KCOV instrumentation after load_segments()&lt;/p&gt;
&lt;p&gt;The load_segments() function changes segment registers, invalidating GS base
(which KCOV relies on for per-cpu data). When CONFIG_KCOV is enabled, any
subsequent instrumented C code call (e.g. native_gdt_invalidate()) begins
crashing the kernel in an endless loop.&lt;/p&gt;
&lt;p&gt;To reproduce the problem, it&amp;amp;apos;s sufficient to do kexec on a KCOV-instrumented
kernel:&lt;/p&gt;
&lt;p&gt;$ kexec -l /boot/otherKernel
  $ kexec -e&lt;/p&gt;
&lt;p&gt;The real-world context for this problem is enabling crash dump collection in
syzkaller. For this, the tool loads a panic kernel before fuzzing and then
calls makedumpfile after the panic. This workflow requires both CONFIG_KEXEC
and CONFIG_KCOV to be enabled simultaneously.&lt;/p&gt;
&lt;p&gt;Adding safeguard…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: 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;xfs: remove xfs_attr_leaf_hasname&lt;/p&gt;
&lt;p&gt;The calling convention of xfs_attr_leaf_hasname() is problematic, because
it returns a NULL buffer when xfs_attr3_leaf_read fails, a valid buffer
when xfs_attr3_leaf_lookup_int returns -ENOATTR or -EEXIST, and a
non-NULL buffer pointer for an already released buffer when
xfs_attr3_leaf_lookup_int fails with other error values.&lt;/p&gt;
&lt;p&gt;Fix this by simply open coding xfs_attr_leaf_hasname in the callers, so
that the buffer release code is done by each caller of
xfs_attr3_leaf_read.(CVE-2026-43153)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;x86/kexec: Disable KCOV instrumentation after load_segments()&lt;/p&gt;
&lt;p&gt;The load_segments() function changes segment registers, invalidating GS base
(which KCOV relies on for per-cpu data). When CONFIG_KCOV is enabled, any
subsequent instrumented C code call (e.g. native_gdt_invalidate()) begins
crashing the kernel in an endless loop.&lt;/p&gt;
&lt;p&gt;To reproduce the problem, it&amp;amp;apos;s sufficient to do kexec on a KCOV-instrumented
kernel:&lt;/p&gt;
&lt;p&gt;$ kexec -l /boot/otherKernel
  $ kexec -e&lt;/p&gt;
&lt;p&gt;The real-world context for this problem is enabling crash dump collection in
syzkaller. For this, the tool loads a panic kernel before fuzzing and then
calls makedumpfile after the panic. This workflow requires both CONFIG_KEXEC
and CONFIG_KCOV to be enabled simultaneously.&lt;/p&gt;
&lt;p&gt;Adding safeguard…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2026-3454</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-52953</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-52953</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 163 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Fix oops due to out of scope access Below oops triggers when kill QEMU process:   Oops: general protection fault, probably for non-canonical address 0x7fffffff844eaaa7: 0000 [#1] SMP NOPTI   Call Trace:    &amp;lt;TASK&amp;gt;    do_raw_spin_lock+0xaa/0xc0    _raw_spin_lock_irqsave+0x21/0x40    domain_remove_dev_pasid+0x52/0x160    intel_nested_set_dev_pasid+0x1b9/0x1e0    __iommu_set_group_pasid+0x56/0x120    pci_dev_reset_iommu_done+0xe3/0x180    pcie_flr+0x65/0x160    __pci_reset_function_locked+0x5b/0x120    vfio_pci_core_close_device+0x63/0xe0 [vfio_pci_core]    vfio_df_close+0x4f/0xa0    vfio_df_unbind_iommufd+0x2d/0x60    vfio_device_fops_release+0x3e/0x40    __fput+0xe5/0x2c0    task_work_run+0x58/0xa0    do_exit+0x2c8/0x600    do_group_exit+0x2f/0xa0    get_signal+0x863/0x8c0    arch_do_signal_or_restart+0x24/0x100    exit_to_user_mode_loop+0x87/0x380    do_syscall_64+0x2ff/0x11e0    entry_SYSCALL_64_after_hwframe+0x76/0x7e The global static blocked domain is a dummy domain without corresponding dmar_domain structure, accessing beyond iommu_domain structure triggers oops easily. Fix it by return early in domain_remove_dev_pasid() like identity domain.&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 163 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Fix oops due to out of scope access Below oops triggers when kill QEMU process:   Oops: general protection fault, probably for non-canonical address 0x7fffffff844eaaa7: 0000 [#1] SMP NOPTI   Call Trace:    &amp;lt;TASK&amp;gt;    do_raw_spin_lock+0xaa/0xc0    _raw_spin_lock_irqsave+0x21/0x40    domain_remove_dev_pasid+0x52/0x160    intel_nested_set_dev_pasid+0x1b9/0x1e0    __iommu_set_group_pasid+0x56/0x120    pci_dev_reset_iommu_done+0xe3/0x180    pcie_flr+0x65/0x160    __pci_reset_function_locked+0x5b/0x120    vfio_pci_core_close_device+0x63/0xe0 [vfio_pci_core]    vfio_df_close+0x4f/0xa0    vfio_df_unbind_iommufd+0x2d/0x60    vfio_device_fops_release+0x3e/0x40    __fput+0xe5/0x2c0    task_work_run+0x58/0xa0    do_exit+0x2c8/0x600    do_group_exit+0x2f/0xa0    get_signal+0x863/0x8c0    arch_do_signal_or_restart+0x24/0x100    exit_to_user_mode_loop+0x87/0x380    do_syscall_64+0x2ff/0x11e0    entry_SYSCALL_64_after_hwframe+0x76/0x7e The global static blocked domain is a dummy domain without corresponding dmar_domain structure, accessing beyond iommu_domain structure triggers oops easily. Fix it by return early in domain_remove_dev_pasid() like identity domain.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-52953</guid>
    </item>
  </channel>
</rss>
