<?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>Thu, 19 Nov 2026 18:35:21 +0000</lastBuildDate>
    <item>
      <title>ALSA-2026:97040 — Important: kernel security, bug fix, and enhancement update</title>
      <link>https://127.0.0.1:10001/vuln/alsa-2026:97040</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:10: kernel, AlmaLinux:10: kernel-64k, AlmaLinux:10: kernel-64k-core, AlmaLinux:10: kernel-64k-debug, AlmaLinux:10: kernel-64k-debug-core, AlmaLinux:10: kernel-64k-debug-devel, AlmaLinux:10: kernel-64k-debug-devel-matched, AlmaLinux:10: kernel-64k-debug-modules, AlmaLinux:10: kernel-64k-debug-modules-core, AlmaLinux:10: kernel-64k-debug-modules-extra and 65 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: Linux kernel: Denial of Service via unsafe requeue in rxrpc_recvmsg (CVE-2026-23066)
  * kernel: Kernel: Race condition in espintcp can lead to denial of service (CVE-2026-23239)
  * kernel: Linux kernel: Denial of service due to a race condition in the TLS subsystem (CVE-2026-23240)
  * kernel: Linux kernel: xfrm single-frag length not properly limited ()
  * kernel: ext4: fix e4b bitmap inconsistency reports (CVE-2026-45942)
  * kernel: Revert &amp;#34;wireguard: device: enable threaded NAPI&amp;#34; (CVE-2026-52945)
  * kernel: iommu: Fix WARN_ON in __iommu_group_set_domain_nofail() due to reset (CVE-2026-52952)
  * kernel: nfsd: fix dead ACL conflict guard in nfsd4_create (CVE-2026-53395)
  * kernel: pNFS: Fix use-after-free in pnfs_update_layout() (CVE-2026-63800)
  * kernel: nvme-pci: fix dma_vecs leak on p2p memory (CVE-2026-64020)
  * kernel: xfrm: route MIGRATE notifications to caller&amp;#39;s netns (CVE-2026-63914)
  * kernel: bpf, skmsg: fix verdict sk_data_ready racing with ktls rx (CVE-2026-64025)
  * kernel: ethtool: coalesce: cap profile updates at NET_DIM_PARAMS_NUM_PROFILES (CVE-2026-63987)
  * kernel: net: hsr: fix potential OOB access in supervision frame handling (CVE-2026-64000)
  * kernel: bpf: Reject fragmented frames in devmap (CVE-2026-64355)
  * kernel: net/handshake: Take a long-lived file reference at submit (CVE-2026-64523)
  * kernel: i2c: core: fi…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:10: kernel, AlmaLinux:10: kernel-64k, AlmaLinux:10: kernel-64k-core, AlmaLinux:10: kernel-64k-debug, AlmaLinux:10: kernel-64k-debug-core, AlmaLinux:10: kernel-64k-debug-devel, AlmaLinux:10: kernel-64k-debug-devel-matched, AlmaLinux:10: kernel-64k-debug-modules, AlmaLinux:10: kernel-64k-debug-modules-core, AlmaLinux:10: kernel-64k-debug-modules-extra and 65 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: Linux kernel: Denial of Service via unsafe requeue in rxrpc_recvmsg (CVE-2026-23066)
  * kernel: Kernel: Race condition in espintcp can lead to denial of service (CVE-2026-23239)
  * kernel: Linux kernel: Denial of service due to a race condition in the TLS subsystem (CVE-2026-23240)
  * kernel: Linux kernel: xfrm single-frag length not properly limited ()
  * kernel: ext4: fix e4b bitmap inconsistency reports (CVE-2026-45942)
  * kernel: Revert &amp;#34;wireguard: device: enable threaded NAPI&amp;#34; (CVE-2026-52945)
  * kernel: iommu: Fix WARN_ON in __iommu_group_set_domain_nofail() due to reset (CVE-2026-52952)
  * kernel: nfsd: fix dead ACL conflict guard in nfsd4_create (CVE-2026-53395)
  * kernel: pNFS: Fix use-after-free in pnfs_update_layout() (CVE-2026-63800)
  * kernel: nvme-pci: fix dma_vecs leak on p2p memory (CVE-2026-64020)
  * kernel: xfrm: route MIGRATE notifications to caller&amp;#39;s netns (CVE-2026-63914)
  * kernel: bpf, skmsg: fix verdict sk_data_ready racing with ktls rx (CVE-2026-64025)
  * kernel: ethtool: coalesce: cap profile updates at NET_DIM_PARAMS_NUM_PROFILES (CVE-2026-63987)
  * kernel: net: hsr: fix potential OOB access in supervision frame handling (CVE-2026-64000)
  * kernel: bpf: Reject fragmented frames in devmap (CVE-2026-64355)
  * kernel: net/handshake: Take a long-lived file reference at submit (CVE-2026-64523)
  * kernel: i2c: core: fi…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/alsa-2026:97040</guid>
    </item>
    <item>
      <title>Withdrawn: BELL-CVE-2026-52952 — CVE-2026-52952 does not affect BellSoft software</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-52952</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2026-52952</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>UBUNTU-CVE-2026-52952</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-52952</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 108 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: iommu: Fix WARN_ON in __iommu_group_set_domain_nofail() due to reset In __iommu_group_set_domain_internal(), concurrent domain attachments are rejected when any device in the group is recovering. This is necessary to fence concurrent attachments to a multi-device group where devices might share the same RID due to PCI DMA alias quirks, but triggers the WARN_ON in __iommu_group_set_domain_nofail(). Other IOMMU_SET_DOMAIN_MUST_SUCCEED callers in detach/teardown paths, such as __iommu_group_set_core_domain and __iommu_release_dma_ownership, should not be rejected, as the domain would be freed anyway in these nofail paths while group-&amp;gt;domain is still pointing to it. So pci_dev_reset_iommu_done() could trigger a UAF when re-attaching group-&amp;gt;domain. Honor the IOMMU_SET_DOMAIN_MUST_SUCCEED flag, allowing the callers through the group-&amp;gt;recovery_cnt fence, so as to update the group-&amp;gt;domain pointer. Instead add a gdev-&amp;gt;blocked check in the device iteration loop, to prevent any concurrent per-device detachment.&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 108 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: iommu: Fix WARN_ON in __iommu_group_set_domain_nofail() due to reset In __iommu_group_set_domain_internal(), concurrent domain attachments are rejected when any device in the group is recovering. This is necessary to fence concurrent attachments to a multi-device group where devices might share the same RID due to PCI DMA alias quirks, but triggers the WARN_ON in __iommu_group_set_domain_nofail(). Other IOMMU_SET_DOMAIN_MUST_SUCCEED callers in detach/teardown paths, such as __iommu_group_set_core_domain and __iommu_release_dma_ownership, should not be rejected, as the domain would be freed anyway in these nofail paths while group-&amp;gt;domain is still pointing to it. So pci_dev_reset_iommu_done() could trigger a UAF when re-attaching group-&amp;gt;domain. Honor the IOMMU_SET_DOMAIN_MUST_SUCCEED flag, allowing the callers through the group-&amp;gt;recovery_cnt fence, so as to update the group-&amp;gt;domain pointer. Instead add a gdev-&amp;gt;blocked check in the device iteration loop, to prevent any concurrent per-device detachment.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-52952</guid>
    </item>
  </channel>
</rss>
