<?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 13:06:45 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-43214</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-43214</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-43214</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0697 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-0697</link>
      <description>certfr-2026-avi-0697</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0697</guid>
    </item>
    <item>
      <title>OESA-2026-2312 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2026-2312</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;dmaengine: idxd: fix possible wrong descriptor completion in llist_abort_desc()&lt;/p&gt;
&lt;p&gt;At the end of this function, d is the traversal cursor of flist, but the
code completes found instead. This can lead to issues such as NULL pointer
dereferences, double completion, or descriptor leaks.&lt;/p&gt;
&lt;p&gt;Fix this by completing d instead of found in the final
list_for_each_entry_safe() loop.(CVE-2026-31436)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;hwmon: (pmbus/core) Protect regulator operations with mutex&lt;/p&gt;
&lt;p&gt;The regulator operations pmbus_regulator_get_voltage(),
pmbus_regulator_set_voltage(), and pmbus_regulator_list_voltage()
access PMBus registers and shared data but were not protected by
the update_lock mutex. This could lead to race conditions.&lt;/p&gt;
&lt;p&gt;However, adding mutex protection directly to these functions causes
a deadlock because pmbus_regulator_notify() (which calls
regulator_notifier_call_chain()) is often called with the mutex
already held (e.g., from pmbus_fault_handler()). If a regulator
callback then calls one of the now-protected voltage functions,
it will attempt to acquire the same mutex.&lt;/p&gt;
&lt;p&gt;Rework pmbus_regulator_notify() to utilize a worker function to
send notifications outside of the mutex protection. Events are
stored as atomics in a per-page bitmask and processed by the worker.&lt;/p&gt;
&lt;p&gt;Initialize the worker and its as…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;dmaengine: idxd: fix possible wrong descriptor completion in llist_abort_desc()&lt;/p&gt;
&lt;p&gt;At the end of this function, d is the traversal cursor of flist, but the
code completes found instead. This can lead to issues such as NULL pointer
dereferences, double completion, or descriptor leaks.&lt;/p&gt;
&lt;p&gt;Fix this by completing d instead of found in the final
list_for_each_entry_safe() loop.(CVE-2026-31436)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;hwmon: (pmbus/core) Protect regulator operations with mutex&lt;/p&gt;
&lt;p&gt;The regulator operations pmbus_regulator_get_voltage(),
pmbus_regulator_set_voltage(), and pmbus_regulator_list_voltage()
access PMBus registers and shared data but were not protected by
the update_lock mutex. This could lead to race conditions.&lt;/p&gt;
&lt;p&gt;However, adding mutex protection directly to these functions causes
a deadlock because pmbus_regulator_notify() (which calls
regulator_notifier_call_chain()) is often called with the mutex
already held (e.g., from pmbus_fault_handler()). If a regulator
callback then calls one of the now-protected voltage functions,
it will attempt to acquire the same mutex.&lt;/p&gt;
&lt;p&gt;Rework pmbus_regulator_notify() to utilize a worker function to
send notifications outside of the mutex protection. Events are
stored as atomics in a per-page bitmask and processed by the worker.&lt;/p&gt;
&lt;p&gt;Initialize the worker and its as…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2026-2312</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-43214</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-43214</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 179 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Add SRCU protection for reading PDPTRs in __get_sregs2() Add SRCU read-side protection when reading PDPTR registers in __get_sregs2(). Reading PDPTRs may trigger access to guest memory: kvm_pdptr_read() -&amp;gt; svm_cache_reg() -&amp;gt; load_pdptrs() -&amp;gt; kvm_vcpu_read_guest_page() -&amp;gt; kvm_vcpu_gfn_to_memslot() kvm_vcpu_gfn_to_memslot() dereferences memslots via __kvm_memslots(), which uses srcu_dereference_check() and requires either kvm-&amp;gt;srcu or kvm-&amp;gt;slots_lock to be held. Currently only vcpu-&amp;gt;mutex is held, triggering lockdep warning: ============================= WARNING: suspicious RCU usage in kvm_vcpu_gfn_to_memslot 6.12.59+ #3 Not tainted include/linux/kvm_host.h:1062 suspicious rcu_dereference_check() usage! other info that might help us debug this: rcu_scheduler_active = 2, debug_locks = 1 1 lock held by syz.5.1717/15100:  #0: ff1100002f4b00b0 (&amp;amp;vcpu-&amp;gt;mutex){+.+.}-{3:3}, at: kvm_vcpu_ioctl+0x1d5/0x1590 Call Trace:  &amp;lt;TASK&amp;gt;  __dump_stack lib/dump_stack.c:94 [inline]  dump_stack_lvl+0xf0/0x120 lib/dump_stack.c:120  lockdep_rcu_suspicious+0x1e3/0x270 kernel/locking/lockdep.c:6824  __kvm_memslots include/linux/kvm_host.h:1062 [inline]  __kvm_memslots include/linux/kvm_host.h:1059 [inline]  kvm_vcpu_memslots include/linux/kvm_host.h:1076 [inline]  kvm_vcpu_gfn_to_memslot+0x518/0x5e0 virt/kvm/kvm_main.c:2617  kvm_vcpu_read_guest_page+0x27/0x50 virt/kvm/kvm_main.c:3302  load_pdptrs+0xff/0x4b0 arch/x86/kvm/x86.c…&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 179 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Add SRCU protection for reading PDPTRs in __get_sregs2() Add SRCU read-side protection when reading PDPTR registers in __get_sregs2(). Reading PDPTRs may trigger access to guest memory: kvm_pdptr_read() -&amp;gt; svm_cache_reg() -&amp;gt; load_pdptrs() -&amp;gt; kvm_vcpu_read_guest_page() -&amp;gt; kvm_vcpu_gfn_to_memslot() kvm_vcpu_gfn_to_memslot() dereferences memslots via __kvm_memslots(), which uses srcu_dereference_check() and requires either kvm-&amp;gt;srcu or kvm-&amp;gt;slots_lock to be held. Currently only vcpu-&amp;gt;mutex is held, triggering lockdep warning: ============================= WARNING: suspicious RCU usage in kvm_vcpu_gfn_to_memslot 6.12.59+ #3 Not tainted include/linux/kvm_host.h:1062 suspicious rcu_dereference_check() usage! other info that might help us debug this: rcu_scheduler_active = 2, debug_locks = 1 1 lock held by syz.5.1717/15100:  #0: ff1100002f4b00b0 (&amp;amp;vcpu-&amp;gt;mutex){+.+.}-{3:3}, at: kvm_vcpu_ioctl+0x1d5/0x1590 Call Trace:  &amp;lt;TASK&amp;gt;  __dump_stack lib/dump_stack.c:94 [inline]  dump_stack_lvl+0xf0/0x120 lib/dump_stack.c:120  lockdep_rcu_suspicious+0x1e3/0x270 kernel/locking/lockdep.c:6824  __kvm_memslots include/linux/kvm_host.h:1062 [inline]  __kvm_memslots include/linux/kvm_host.h:1059 [inline]  kvm_vcpu_memslots include/linux/kvm_host.h:1076 [inline]  kvm_vcpu_gfn_to_memslot+0x518/0x5e0 virt/kvm/kvm_main.c:2617  kvm_vcpu_read_guest_page+0x27/0x50 virt/kvm/kvm_main.c:3302  load_pdptrs+0xff/0x4b0 arch/x86/kvm/x86.c…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-43214</guid>
    </item>
  </channel>
</rss>
