<?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 00:45:30 +0000</lastBuildDate>
    <item>
      <title>ALSA-2026:36956 — Important: kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/alsa-2026:36956</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: net/sched: ets: Always remove class from active list before deleting in ets_qdisc_change (CVE-2025-71066)
  * kernel: sctp: revalidate list cursor after sctp_sendmsg_to_asoc() in SCTP_SENDALL (CVE-2026-46227)
  * kernel: KVM: x86: Fix shadow paging use-after-free due to unexpected GFN (CVE-2026-46113)
  * kernel: KVM: x86: Fix shadow paging use-after-free due to unexpected role (CVE-2026-53359)&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: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: net/sched: ets: Always remove class from active list before deleting in ets_qdisc_change (CVE-2025-71066)
  * kernel: sctp: revalidate list cursor after sctp_sendmsg_to_asoc() in SCTP_SENDALL (CVE-2026-46227)
  * kernel: KVM: x86: Fix shadow paging use-after-free due to unexpected GFN (CVE-2026-46113)
  * kernel: KVM: x86: Fix shadow paging use-after-free due to unexpected role (CVE-2026-53359)&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:36956</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-46113</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-46113</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-46113</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0731 — De multiples vulnérabilités ont été découvertes dans les produits Microsoft. Certaines d'entre elles permettent à un at…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-0731</link>
      <description>certfr-2026-avi-0731</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0731</guid>
    </item>
    <item>
      <title>OESA-2026-3453 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2026-3453</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;wifi: cfg80211: cancel rfkill_block work in wiphy_unregister()&lt;/p&gt;
&lt;p&gt;There is a use-after-free error in cfg80211_shutdown_all_interfaces found
by syzkaller:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: use-after-free in cfg80211_shutdown_all_interfaces+0x213/0x220
Read of size 8 at addr ffff888112a78d98 by task kworker/0:5/5326
CPU: 0 UID: 0 PID: 5326 Comm: kworker/0:5 Not tainted 6.19.0-rc2 #2 PREEMPT(voluntary)
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014
Workqueue: events cfg80211_rfkill_block_work
Call Trace:
 &amp;amp;lt;TASK&amp;amp;gt;
 dump_stack_lvl+0x116/0x1f0
 print_report+0xcd/0x630
 kasan_report+0xe0/0x110
 cfg80211_shutdown_all_interfaces+0x213/0x220
 cfg80211_rfkill_block_work+0x1e/0x30
 process_one_work+0x9cf/0x1b70
 worker_thread+0x6c8/0xf10
 kthread+0x3c5/0x780
 ret_from_fork+0x56d/0x700
 ret_from_fork_asm+0x1a/0x30
 &amp;amp;lt;/TASK&amp;amp;gt;&lt;/p&gt;
&lt;p&gt;The problem arises due to the rfkill_block work is not cancelled when wiphy
is being unregistered. In order to fix the issue cancel the corresponding
work in wiphy_unregister().&lt;/p&gt;
&lt;p&gt;Found by Linux Verification Center (linuxtesting.org) with Syzkaller.(CVE-2026-23336)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: L2CAP: Fix type confusion in l2cap_ecred_reconf_rsp()&lt;/p&gt;
&lt;p&gt;l2cap_ecred_reconf_rsp() casts the incoming data to struct
l2cap_ecred_conn_rsp (the ECRED *connection* respons…&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;wifi: cfg80211: cancel rfkill_block work in wiphy_unregister()&lt;/p&gt;
&lt;p&gt;There is a use-after-free error in cfg80211_shutdown_all_interfaces found
by syzkaller:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: use-after-free in cfg80211_shutdown_all_interfaces+0x213/0x220
Read of size 8 at addr ffff888112a78d98 by task kworker/0:5/5326
CPU: 0 UID: 0 PID: 5326 Comm: kworker/0:5 Not tainted 6.19.0-rc2 #2 PREEMPT(voluntary)
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014
Workqueue: events cfg80211_rfkill_block_work
Call Trace:
 &amp;amp;lt;TASK&amp;amp;gt;
 dump_stack_lvl+0x116/0x1f0
 print_report+0xcd/0x630
 kasan_report+0xe0/0x110
 cfg80211_shutdown_all_interfaces+0x213/0x220
 cfg80211_rfkill_block_work+0x1e/0x30
 process_one_work+0x9cf/0x1b70
 worker_thread+0x6c8/0xf10
 kthread+0x3c5/0x780
 ret_from_fork+0x56d/0x700
 ret_from_fork_asm+0x1a/0x30
 &amp;amp;lt;/TASK&amp;amp;gt;&lt;/p&gt;
&lt;p&gt;The problem arises due to the rfkill_block work is not cancelled when wiphy
is being unregistered. In order to fix the issue cancel the corresponding
work in wiphy_unregister().&lt;/p&gt;
&lt;p&gt;Found by Linux Verification Center (linuxtesting.org) with Syzkaller.(CVE-2026-23336)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: L2CAP: Fix type confusion in l2cap_ecred_reconf_rsp()&lt;/p&gt;
&lt;p&gt;l2cap_ecred_reconf_rsp() casts the incoming data to struct
l2cap_ecred_conn_rsp (the ECRED *connection* respons…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2026-3453</guid>
    </item>
    <item>
      <title>RLSA-2026:36956 — Important: kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/rlsa-2026:36956</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:10: rv, Rocky Linux:10: kernel, Rocky Linux:10: kernel-debug-modules-core, Rocky Linux:10: kernel-debug-debuginfo, Rocky Linux:10: perf-debuginfo, Rocky Linux:10: kernel-modules-extra, Rocky Linux:10: libperf, Rocky Linux:10: kernel-debuginfo, Rocky Linux:10: kernel-core, Rocky Linux:10: perf 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: net/sched: ets: Always remove class from active list before deleting in ets_qdisc_change (CVE-2025-71066)&lt;/p&gt;
&lt;p&gt;* kernel: sctp: revalidate list cursor after sctp_sendmsg_to_asoc() in SCTP_SENDALL (CVE-2026-46227)&lt;/p&gt;
&lt;p&gt;* kernel: KVM: x86: Fix shadow paging use-after-free due to unexpected GFN (CVE-2026-46113)&lt;/p&gt;
&lt;p&gt;* kernel: KVM: x86: Fix shadow paging use-after-free due to unexpected role (CVE-2026-53359)&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:10: rv, Rocky Linux:10: kernel, Rocky Linux:10: kernel-debug-modules-core, Rocky Linux:10: kernel-debug-debuginfo, Rocky Linux:10: perf-debuginfo, Rocky Linux:10: kernel-modules-extra, Rocky Linux:10: libperf, Rocky Linux:10: kernel-debuginfo, Rocky Linux:10: kernel-core, Rocky Linux:10: perf 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: net/sched: ets: Always remove class from active list before deleting in ets_qdisc_change (CVE-2025-71066)&lt;/p&gt;
&lt;p&gt;* kernel: sctp: revalidate list cursor after sctp_sendmsg_to_asoc() in SCTP_SENDALL (CVE-2026-46227)&lt;/p&gt;
&lt;p&gt;* kernel: KVM: x86: Fix shadow paging use-after-free due to unexpected GFN (CVE-2026-46113)&lt;/p&gt;
&lt;p&gt;* kernel: KVM: x86: Fix shadow paging use-after-free due to unexpected role (CVE-2026-53359)&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:36956</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-46113</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-46113</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 255 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Fix shadow paging use-after-free due to unexpected GFN The shadow MMU computes GFNs for direct shadow pages using sp-&amp;gt;gfn plus the SPTE index. This assumption breaks for shadow paging if the guest page tables are modified between VM entries (similar to commit aad885e77496, &amp;#34;KVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE&amp;#34;, 2026-03-27).  The flow is as follows: - a PDE is installed for a 2MB mapping, and a page in that area is   accessed.  KVM creates a kvm_mmu_page consisting of 512 4KB pages;   the kvm_mmu_page is marked by FNAME(fetch) as direct-mapped because   the guest&amp;#39;s mapping is a huge page (and thus contiguous). - the PDE mapping is changed from outside the guest. - the guest accesses another page in the same 2MB area.  KVM installs   a new leaf SPTE and rmap entry; the SPTE uses the &amp;#34;correct&amp;#34; GFN   (i.e. based on the new mapping, as changed in the previous step) but   that GFN is outside of the [sp-&amp;gt;gfn, sp-&amp;gt;gfn + 511] range; therefore   the rmap entry cannot be found and removed when the kvm_mmu_page   is zapped. - the memslot that covers the first 2MB mapping is deleted, and the   kvm_mmu_page for the now-invalid GPA is zapped.  However, rmap_remove()   only looks at the [sp-&amp;gt;gfn, sp-&amp;gt;gfn + 511] range established in step 1,   and fails to find the rmap entry that was recorded by step 3. - any operation that causes an rmap walk for the same page accessed   by…&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 255 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Fix shadow paging use-after-free due to unexpected GFN The shadow MMU computes GFNs for direct shadow pages using sp-&amp;gt;gfn plus the SPTE index. This assumption breaks for shadow paging if the guest page tables are modified between VM entries (similar to commit aad885e77496, &amp;#34;KVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE&amp;#34;, 2026-03-27).  The flow is as follows: - a PDE is installed for a 2MB mapping, and a page in that area is   accessed.  KVM creates a kvm_mmu_page consisting of 512 4KB pages;   the kvm_mmu_page is marked by FNAME(fetch) as direct-mapped because   the guest&amp;#39;s mapping is a huge page (and thus contiguous). - the PDE mapping is changed from outside the guest. - the guest accesses another page in the same 2MB area.  KVM installs   a new leaf SPTE and rmap entry; the SPTE uses the &amp;#34;correct&amp;#34; GFN   (i.e. based on the new mapping, as changed in the previous step) but   that GFN is outside of the [sp-&amp;gt;gfn, sp-&amp;gt;gfn + 511] range; therefore   the rmap entry cannot be found and removed when the kvm_mmu_page   is zapped. - the memslot that covers the first 2MB mapping is deleted, and the   kvm_mmu_page for the now-invalid GPA is zapped.  However, rmap_remove()   only looks at the [sp-&amp;gt;gfn, sp-&amp;gt;gfn + 511] range established in step 1,   and fails to find the rmap entry that was recorded by step 3. - any operation that causes an rmap walk for the same page accessed   by…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-46113</guid>
    </item>
  </channel>
</rss>
