<?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://vulnerability.circl.lu</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, 01 Oct 2026 07:35:08 +0000</lastBuildDate>
    <item>
      <title>Withdrawn: BELL-CVE-2026-90181 — CVE-2026-90181 does not affect BellSoft software</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-90181</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://vulnerability.circl.lu/vuln/bell-cve-2026-90181</guid>
    </item>
    <item>
      <title>fkie_cve-2026-90181</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-90181</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ublk: avoid teardown retry loop on xarray allocation failure&lt;/p&gt;
&lt;p&gt;__ublk_shmem_remove_ranges() removes matching maple tree ranges in
batches, but first stores each range into a temporary xarray so that the
pages can be unpinned after dropping the maple tree lock.&lt;/p&gt;
&lt;p&gt;That temporary xarray is filled under the maple tree lock with
xa_store(..., GFP_ATOMIC). If the store fails before mas_erase(), the
current range is left in the tree and the helper returns false. The
outer ublk_shmem_remove_ranges() loop then immediately retries the same
range. While the atomic allocation keeps failing, the teardown path has
no forward progress.&lt;/p&gt;
&lt;p&gt;The issue can be reproduced with radix_tree_node failslab injection after
a SHMEM_ZC buffer has already been registered:&lt;/p&gt;
&lt;p&gt;# Kernel config:
  #   CONFIG_BLK_DEV_UBLK=y
  #   CONFIG_DEBUG_FS=y
  #   CONFIG_FAULT_INJECTION=y
  #   CONFIG_FAULT_INJECTION_DEBUG_FS=y
  #   CONFIG_FAILSLAB=y&lt;/p&gt;
&lt;p&gt;echo 10 &amp;gt; /proc/sys/vm/nr_hugepages
  mkdir -p /tmp/htlb
  mount -t hugetlbfs none /tmp/htlb
  fallocate -l 4M /tmp/htlb/ublk_buf&lt;/p&gt;
&lt;p&gt;dev_id=$(kublk add -t null --shmem_zc \
		--htlb /tmp/htlb/ublk_buf |
	   awk -F &amp;#39;[ :]&amp;#39; &amp;#39;/dev id/ {print $3}&amp;#39;)&lt;/p&gt;
&lt;p&gt;echo 1 &amp;gt; /sys/kernel/slab/radix_tree_node/failslab
  echo Y &amp;gt; /sys/kernel/debug/failslab/cache-filter
  echo Y &amp;gt; /sys/kernel/debug/failslab/ignore-gfp-wait
  echo 1 &amp;gt; /sys/kernel/debug/failslab/interval
  echo -1 &amp;gt; /sys/kernel/debug/failslab/times
  echo 100 &amp;gt; /sy…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ublk: avoid teardown retry loop on xarray allocation failure&lt;/p&gt;
&lt;p&gt;__ublk_shmem_remove_ranges() removes matching maple tree ranges in
batches, but first stores each range into a temporary xarray so that the
pages can be unpinned after dropping the maple tree lock.&lt;/p&gt;
&lt;p&gt;That temporary xarray is filled under the maple tree lock with
xa_store(..., GFP_ATOMIC). If the store fails before mas_erase(), the
current range is left in the tree and the helper returns false. The
outer ublk_shmem_remove_ranges() loop then immediately retries the same
range. While the atomic allocation keeps failing, the teardown path has
no forward progress.&lt;/p&gt;
&lt;p&gt;The issue can be reproduced with radix_tree_node failslab injection after
a SHMEM_ZC buffer has already been registered:&lt;/p&gt;
&lt;p&gt;# Kernel config:
  #   CONFIG_BLK_DEV_UBLK=y
  #   CONFIG_DEBUG_FS=y
  #   CONFIG_FAULT_INJECTION=y
  #   CONFIG_FAULT_INJECTION_DEBUG_FS=y
  #   CONFIG_FAILSLAB=y&lt;/p&gt;
&lt;p&gt;echo 10 &amp;gt; /proc/sys/vm/nr_hugepages
  mkdir -p /tmp/htlb
  mount -t hugetlbfs none /tmp/htlb
  fallocate -l 4M /tmp/htlb/ublk_buf&lt;/p&gt;
&lt;p&gt;dev_id=$(kublk add -t null --shmem_zc \
		--htlb /tmp/htlb/ublk_buf |
	   awk -F &amp;#39;[ :]&amp;#39; &amp;#39;/dev id/ {print $3}&amp;#39;)&lt;/p&gt;
&lt;p&gt;echo 1 &amp;gt; /sys/kernel/slab/radix_tree_node/failslab
  echo Y &amp;gt; /sys/kernel/debug/failslab/cache-filter
  echo Y &amp;gt; /sys/kernel/debug/failslab/ignore-gfp-wait
  echo 1 &amp;gt; /sys/kernel/debug/failslab/interval
  echo -1 &amp;gt; /sys/kernel/debug/failslab/times
  echo 100 &amp;gt; /sy…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-90181</guid>
    </item>
    <item>
      <title>GHSA-6q49-r2pp-pjwc</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-6q49-r2pp-pjwc</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ublk: avoid teardown retry loop on xarray allocation failure&lt;/p&gt;
&lt;p&gt;__ublk_shmem_remove_ranges() removes matching maple tree ranges in
batches, but first stores each range into a temporary xarray so that the
pages can be unpinned after dropping the maple tree lock.&lt;/p&gt;
&lt;p&gt;That temporary xarray is filled under the maple tree lock with
xa_store(..., GFP_ATOMIC). If the store fails before mas_erase(), the
current range is left in the tree and the helper returns false. The
outer ublk_shmem_remove_ranges() loop then immediately retries the same
range. While the atomic allocation keeps failing, the teardown path has
no forward progress.&lt;/p&gt;
&lt;p&gt;The issue can be reproduced with radix_tree_node failslab injection after
a SHMEM_ZC buffer has already been registered:&lt;/p&gt;
&lt;p&gt;# Kernel config:
  #   CONFIG_BLK_DEV_UBLK=y
  #   CONFIG_DEBUG_FS=y
  #   CONFIG_FAULT_INJECTION=y
  #   CONFIG_FAULT_INJECTION_DEBUG_FS=y
  #   CONFIG_FAILSLAB=y&lt;/p&gt;
&lt;p&gt;echo 10 &amp;gt; /proc/sys/vm/nr_hugepages
  mkdir -p /tmp/htlb
  mount -t hugetlbfs none /tmp/htlb
  fallocate -l 4M /tmp/htlb/ublk_buf&lt;/p&gt;
&lt;p&gt;dev_id=$(kublk add -t null --shmem_zc \
		--htlb /tmp/htlb/ublk_buf |
	   awk -F &amp;#39;[ :]&amp;#39; &amp;#39;/dev id/ {print $3}&amp;#39;)&lt;/p&gt;
&lt;p&gt;echo 1 &amp;gt; /sys/kernel/slab/radix_tree_node/failslab
  echo Y &amp;gt; /sys/kernel/debug/failslab/cache-filter
  echo Y &amp;gt; /sys/kernel/debug/failslab/ignore-gfp-wait
  echo 1 &amp;gt; /sys/kernel/debug/failslab/interval
  echo -1 &amp;gt; /sys/kernel/debug/failslab/times
  echo 100 &amp;gt; /sy…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ublk: avoid teardown retry loop on xarray allocation failure&lt;/p&gt;
&lt;p&gt;__ublk_shmem_remove_ranges() removes matching maple tree ranges in
batches, but first stores each range into a temporary xarray so that the
pages can be unpinned after dropping the maple tree lock.&lt;/p&gt;
&lt;p&gt;That temporary xarray is filled under the maple tree lock with
xa_store(..., GFP_ATOMIC). If the store fails before mas_erase(), the
current range is left in the tree and the helper returns false. The
outer ublk_shmem_remove_ranges() loop then immediately retries the same
range. While the atomic allocation keeps failing, the teardown path has
no forward progress.&lt;/p&gt;
&lt;p&gt;The issue can be reproduced with radix_tree_node failslab injection after
a SHMEM_ZC buffer has already been registered:&lt;/p&gt;
&lt;p&gt;# Kernel config:
  #   CONFIG_BLK_DEV_UBLK=y
  #   CONFIG_DEBUG_FS=y
  #   CONFIG_FAULT_INJECTION=y
  #   CONFIG_FAULT_INJECTION_DEBUG_FS=y
  #   CONFIG_FAILSLAB=y&lt;/p&gt;
&lt;p&gt;echo 10 &amp;gt; /proc/sys/vm/nr_hugepages
  mkdir -p /tmp/htlb
  mount -t hugetlbfs none /tmp/htlb
  fallocate -l 4M /tmp/htlb/ublk_buf&lt;/p&gt;
&lt;p&gt;dev_id=$(kublk add -t null --shmem_zc \
		--htlb /tmp/htlb/ublk_buf |
	   awk -F &amp;#39;[ :]&amp;#39; &amp;#39;/dev id/ {print $3}&amp;#39;)&lt;/p&gt;
&lt;p&gt;echo 1 &amp;gt; /sys/kernel/slab/radix_tree_node/failslab
  echo Y &amp;gt; /sys/kernel/debug/failslab/cache-filter
  echo Y &amp;gt; /sys/kernel/debug/failslab/ignore-gfp-wait
  echo 1 &amp;gt; /sys/kernel/debug/failslab/interval
  echo -1 &amp;gt; /sys/kernel/debug/failslab/times
  echo 100 &amp;gt; /sy…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-6q49-r2pp-pjwc</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11880-1 — kernel-devel-7.2.7-1.1 on GA media</title>
      <link>https://vulnerability.circl.lu/vuln/opensuse-su-2026:11880-1</link>
      <description>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/opensuse-su-2026:11880-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-90181</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-90181</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 96 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ublk: avoid teardown retry loop on xarray allocation failure __ublk_shmem_remove_ranges() removes matching maple tree ranges in batches, but first stores each range into a temporary xarray so that the pages can be unpinned after dropping the maple tree lock. That temporary xarray is filled under the maple tree lock with xa_store(..., GFP_ATOMIC). If the store fails before mas_erase(), the current range is left in the tree and the helper returns false. The outer ublk_shmem_remove_ranges() loop then immediately retries the same range. While the atomic allocation keeps failing, the teardown path has no forward progress. The issue can be reproduced with radix_tree_node failslab injection after a SHMEM_ZC buffer has already been registered:   # Kernel config:   #   CONFIG_BLK_DEV_UBLK=y   #   CONFIG_DEBUG_FS=y   #   CONFIG_FAULT_INJECTION=y   #   CONFIG_FAULT_INJECTION_DEBUG_FS=y   #   CONFIG_FAILSLAB=y   echo 10 &amp;gt; /proc/sys/vm/nr_hugepages   mkdir -p /tmp/htlb   mount -t hugetlbfs none /tmp/htlb   fallocate -l 4M /tmp/htlb/ublk_buf   dev_id=$(kublk add -t null --shmem_zc \ 		--htlb /tmp/htlb/ublk_buf | 	   awk -F &amp;#39;[ :]&amp;#39; &amp;#39;/dev id/ {print $3}&amp;#39;)   echo 1 &amp;gt; /sys/kernel/slab/radix_tree_node/failslab   echo Y &amp;gt; /sys/kernel/debug/failslab/cache-filter   echo Y &amp;gt; /sys/kernel/debug/failslab/ignore-gfp-wait   echo 1 &amp;gt; /sys/kernel/debug/failslab/interval   echo -1 &amp;gt; /sys/kernel/debug/failslab/times   echo 100 &amp;gt; /sys/kernel…&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 96 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ublk: avoid teardown retry loop on xarray allocation failure __ublk_shmem_remove_ranges() removes matching maple tree ranges in batches, but first stores each range into a temporary xarray so that the pages can be unpinned after dropping the maple tree lock. That temporary xarray is filled under the maple tree lock with xa_store(..., GFP_ATOMIC). If the store fails before mas_erase(), the current range is left in the tree and the helper returns false. The outer ublk_shmem_remove_ranges() loop then immediately retries the same range. While the atomic allocation keeps failing, the teardown path has no forward progress. The issue can be reproduced with radix_tree_node failslab injection after a SHMEM_ZC buffer has already been registered:   # Kernel config:   #   CONFIG_BLK_DEV_UBLK=y   #   CONFIG_DEBUG_FS=y   #   CONFIG_FAULT_INJECTION=y   #   CONFIG_FAULT_INJECTION_DEBUG_FS=y   #   CONFIG_FAILSLAB=y   echo 10 &amp;gt; /proc/sys/vm/nr_hugepages   mkdir -p /tmp/htlb   mount -t hugetlbfs none /tmp/htlb   fallocate -l 4M /tmp/htlb/ublk_buf   dev_id=$(kublk add -t null --shmem_zc \ 		--htlb /tmp/htlb/ublk_buf | 	   awk -F &amp;#39;[ :]&amp;#39; &amp;#39;/dev id/ {print $3}&amp;#39;)   echo 1 &amp;gt; /sys/kernel/slab/radix_tree_node/failslab   echo Y &amp;gt; /sys/kernel/debug/failslab/cache-filter   echo Y &amp;gt; /sys/kernel/debug/failslab/ignore-gfp-wait   echo 1 &amp;gt; /sys/kernel/debug/failslab/interval   echo -1 &amp;gt; /sys/kernel/debug/failslab/times   echo 100 &amp;gt; /sys/kernel…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-90181</guid>
    </item>
  </channel>
</rss>
