<?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>Sun, 11 Oct 2026 23:43:18 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-35798 — btrfs: fix race in read_extent_buffer_pages()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-35798</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;btrfs: fix race in read_extent_buffer_pages()&lt;/p&gt;
&lt;p&gt;There are reports from tree-checker that detects corrupted nodes,
without any obvious pattern so possibly an overwrite in memory.
After some debugging it turns out there&amp;#39;s a race when reading an extent
buffer the uptodate status can be missed.&lt;/p&gt;
&lt;p&gt;To prevent concurrent reads for the same extent buffer,
read_extent_buffer_pages() performs these checks:&lt;/p&gt;
&lt;p&gt;/* (1) */
    if (test_bit(EXTENT_BUFFER_UPTODATE, &amp;amp;eb-&amp;gt;bflags))
        return 0;&lt;/p&gt;
&lt;p&gt;/* (2) */
    if (test_and_set_bit(EXTENT_BUFFER_READING, &amp;amp;eb-&amp;gt;bflags))
        goto done;&lt;/p&gt;
&lt;p&gt;At this point, it seems safe to start the actual read operation. Once
that completes, end_bbio_meta_read() does&lt;/p&gt;
&lt;p&gt;/* (3) */
    set_extent_buffer_uptodate(eb);&lt;/p&gt;
&lt;p&gt;/* (4) */
    clear_bit(EXTENT_BUFFER_READING, &amp;amp;eb-&amp;gt;bflags);&lt;/p&gt;
&lt;p&gt;Normally, this is enough to ensure only one read happens, and all other
callers wait for it to finish before returning.  Unfortunately, there is
a racey interleaving:&lt;/p&gt;
&lt;p&gt;Thread A | Thread B | Thread C
    ---------+----------+---------
       (1)   |          |
             |    (1)   |
       (2)   |          |
       (3)   |          |
       (4)   |          |
             |    (2)   |
             |          |    (1)&lt;/p&gt;
&lt;p&gt;When this happens, thread B kicks of an unnecessary read. Worse, thread
C will see UPTODATE set and return immediately, while the read from
thread B is still in progress.  This race could r…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;btrfs: fix race in read_extent_buffer_pages()&lt;/p&gt;
&lt;p&gt;There are reports from tree-checker that detects corrupted nodes,
without any obvious pattern so possibly an overwrite in memory.
After some debugging it turns out there&amp;#39;s a race when reading an extent
buffer the uptodate status can be missed.&lt;/p&gt;
&lt;p&gt;To prevent concurrent reads for the same extent buffer,
read_extent_buffer_pages() performs these checks:&lt;/p&gt;
&lt;p&gt;/* (1) */
    if (test_bit(EXTENT_BUFFER_UPTODATE, &amp;amp;eb-&amp;gt;bflags))
        return 0;&lt;/p&gt;
&lt;p&gt;/* (2) */
    if (test_and_set_bit(EXTENT_BUFFER_READING, &amp;amp;eb-&amp;gt;bflags))
        goto done;&lt;/p&gt;
&lt;p&gt;At this point, it seems safe to start the actual read operation. Once
that completes, end_bbio_meta_read() does&lt;/p&gt;
&lt;p&gt;/* (3) */
    set_extent_buffer_uptodate(eb);&lt;/p&gt;
&lt;p&gt;/* (4) */
    clear_bit(EXTENT_BUFFER_READING, &amp;amp;eb-&amp;gt;bflags);&lt;/p&gt;
&lt;p&gt;Normally, this is enough to ensure only one read happens, and all other
callers wait for it to finish before returning.  Unfortunately, there is
a racey interleaving:&lt;/p&gt;
&lt;p&gt;Thread A | Thread B | Thread C
    ---------+----------+---------
       (1)   |          |
             |    (1)   |
       (2)   |          |
       (3)   |          |
       (4)   |          |
             |    (2)   |
             |          |    (1)&lt;/p&gt;
&lt;p&gt;When this happens, thread B kicks of an unnecessary read. Worse, thread
C will see UPTODATE set and return immediately, while the read from
thread B is still in progress.  This race could r…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-35798</guid>
    </item>
    <item>
      <title>USN-6816-1 — linux, linux-ibm, linux-lowlatency, linux-raspi vulnerabilities</title>
      <link>https://vulnerability.circl.lu/vuln/usn-6816-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux, Ubuntu:24.04:LTS: linux-ibm, Ubuntu:24.04:LTS: linux-lowlatency, Ubuntu:24.04:LTS: linux-raspi&lt;/p&gt;
&lt;p&gt;Ziming Zhang discovered that the DRM driver for VMware Virtual GPU did not
properly handle certain error conditions, leading to a NULL pointer
dereference. A local attacker could possibly trigger this vulnerability to
cause a denial of service. (CVE-2022-38096)&lt;/p&gt;
&lt;p&gt;Zheng Wang discovered that the Broadcom FullMAC WLAN driver in the Linux
kernel contained a race condition during device removal, leading to a use-
after-free vulnerability. A physically proximate attacker could possibly
use this to cause a denial of service (system crash). (CVE-2023-47233)&lt;/p&gt;
&lt;p&gt;It was discovered that the ATA over Ethernet (AoE) driver in the Linux
kernel contained a race condition, leading to a use-after-free
vulnerability. An attacker could use this to cause a denial of service or
possibly execute arbitrary code. (CVE-2023-6270)&lt;/p&gt;
&lt;p&gt;It was discovered that the Atheros 802.11ac wireless driver did not
properly validate certain data structures, leading to a NULL pointer
dereference. An attacker could possibly use this to cause a denial of
service. (CVE-2023-7042)&lt;/p&gt;
&lt;p&gt;It was discovered that the Intel Data Streaming and Intel Analytics
Accelerator drivers in the Linux kernel allowed direct access to the
devices for unprivileged users and virtual machines. A local attacker could
use this to cause a denial of service. (CVE-2024-21823)&lt;/p&gt;
&lt;p&gt;Gui-Dong Han discovered that the software RAID driver in the Linux kernel
contained a race condition, leading to an integer overflow vulnerability. A
privileged attacker could possib…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux, Ubuntu:24.04:LTS: linux-ibm, Ubuntu:24.04:LTS: linux-lowlatency, Ubuntu:24.04:LTS: linux-raspi&lt;/p&gt;
&lt;p&gt;Ziming Zhang discovered that the DRM driver for VMware Virtual GPU did not
properly handle certain error conditions, leading to a NULL pointer
dereference. A local attacker could possibly trigger this vulnerability to
cause a denial of service. (CVE-2022-38096)&lt;/p&gt;
&lt;p&gt;Zheng Wang discovered that the Broadcom FullMAC WLAN driver in the Linux
kernel contained a race condition during device removal, leading to a use-
after-free vulnerability. A physically proximate attacker could possibly
use this to cause a denial of service (system crash). (CVE-2023-47233)&lt;/p&gt;
&lt;p&gt;It was discovered that the ATA over Ethernet (AoE) driver in the Linux
kernel contained a race condition, leading to a use-after-free
vulnerability. An attacker could use this to cause a denial of service or
possibly execute arbitrary code. (CVE-2023-6270)&lt;/p&gt;
&lt;p&gt;It was discovered that the Atheros 802.11ac wireless driver did not
properly validate certain data structures, leading to a NULL pointer
dereference. An attacker could possibly use this to cause a denial of
service. (CVE-2023-7042)&lt;/p&gt;
&lt;p&gt;It was discovered that the Intel Data Streaming and Intel Analytics
Accelerator drivers in the Linux kernel allowed direct access to the
devices for unprivileged users and virtual machines. A local attacker could
use this to cause a denial of service. (CVE-2024-21823)&lt;/p&gt;
&lt;p&gt;Gui-Dong Han discovered that the software RAID driver in the Linux kernel
contained a race condition, leading to an integer overflow vulnerability. A
privileged attacker could possib…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/usn-6816-1</guid>
    </item>
  </channel>
</rss>
