<?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://cve.radiocsirt.org</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>Wed, 07 Oct 2026 08:01:46 +0000</lastBuildDate>
    <item>
      <title>UBUNTU-CVE-2022-48943</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-48943</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 122 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: KVM: x86/mmu: make apf token non-zero to fix bug In current async pagefault logic, when a page is ready, KVM relies on kvm_arch_can_dequeue_async_page_present() to determine whether to deliver a READY event to the Guest. This function test token value of struct kvm_vcpu_pv_apf_data, which must be reset to zero by Guest kernel when a READY event is finished by Guest. If value is zero meaning that a READY event is done, so the KVM can deliver another. But the kvm_arch_setup_async_pf() may produce a valid token with zero value, which is confused with previous mention and may lead the loss of this READY event. This bug may cause task blocked forever in Guest:  INFO: task stress:7532 blocked for more than 1254 seconds.        Not tainted 5.10.0 #16  &amp;#34;echo 0 &amp;gt; /proc/sys/kernel/hung_task_timeout_secs&amp;#34; disables this message.  task:stress          state:D stack:    0 pid: 7532 ppid:  1409  flags:0x00000080  Call Trace:   __schedule+0x1e7/0x650   schedule+0x46/0xb0   kvm_async_pf_task_wait_schedule+0xad/0xe0   ? exit_to_user_mode_prepare+0x60/0x70   __kvm_handle_async_pf+0x4f/0xb0   ? asm_exc_page_fault+0x8/0x30   exc_page_fault+0x6f/0x110   ? asm_exc_page_fault+0x8/0x30   asm_exc_page_fault+0x1e/0x30  RIP: 0033:0x402d00  RSP: 002b:00007ffd31912500 EFLAGS: 00010206  RAX: 0000000000071000 RBX: ffffffffffffffff RCX: 00000000021a32b0  RDX: 000000000007d011 RSI: 000000000007d000 RDI: 00000000021262b0  RBP: 00000000021262b…&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 122 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: KVM: x86/mmu: make apf token non-zero to fix bug In current async pagefault logic, when a page is ready, KVM relies on kvm_arch_can_dequeue_async_page_present() to determine whether to deliver a READY event to the Guest. This function test token value of struct kvm_vcpu_pv_apf_data, which must be reset to zero by Guest kernel when a READY event is finished by Guest. If value is zero meaning that a READY event is done, so the KVM can deliver another. But the kvm_arch_setup_async_pf() may produce a valid token with zero value, which is confused with previous mention and may lead the loss of this READY event. This bug may cause task blocked forever in Guest:  INFO: task stress:7532 blocked for more than 1254 seconds.        Not tainted 5.10.0 #16  &amp;#34;echo 0 &amp;gt; /proc/sys/kernel/hung_task_timeout_secs&amp;#34; disables this message.  task:stress          state:D stack:    0 pid: 7532 ppid:  1409  flags:0x00000080  Call Trace:   __schedule+0x1e7/0x650   schedule+0x46/0xb0   kvm_async_pf_task_wait_schedule+0xad/0xe0   ? exit_to_user_mode_prepare+0x60/0x70   __kvm_handle_async_pf+0x4f/0xb0   ? asm_exc_page_fault+0x8/0x30   exc_page_fault+0x6f/0x110   ? asm_exc_page_fault+0x8/0x30   asm_exc_page_fault+0x1e/0x30  RIP: 0033:0x402d00  RSP: 002b:00007ffd31912500 EFLAGS: 00010206  RAX: 0000000000071000 RBX: ffffffffffffffff RCX: 00000000021a32b0  RDX: 000000000007d011 RSI: 000000000007d000 RDI: 00000000021262b0  RBP: 00000000021262b…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-48943</guid>
    </item>
  </channel>
</rss>
