<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://127.0.0.1:10001/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-21T12:49:42.864995+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://127.0.0.1:10001" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://127.0.0.1:10001/vuln/bell-cve-2024-35798</id>
    <title>BELL-CVE-2024-35798</title>
    <updated>2026-11-21T12:49:42.871308+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/bell-cve-2024-35798"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2024-avi-0546</id>
    <title>certfr-2024-avi-0546 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
    <updated>2026-11-21T12:49:42.871407+00:00</updated>
    <content>certfr-2024-avi-0546</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2024-avi-0546"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-35798</id>
    <title>UBUNTU-CVE-2024-35798</title>
    <updated>2026-11-21T12:49:42.871435+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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 78 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: btrfs: fix race in read_extent_buffer_pages() 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's a race when reading an extent buffer the uptodate status can be missed. To prevent concurrent reads for the same extent buffer, read_extent_buffer_pages() performs these checks:     /* (1) */     if (test_bit(EXTENT_BUFFER_UPTODATE, &amp;eb-&gt;bflags))         return 0;     /* (2) */     if (test_and_set_bit(EXTENT_BUFFER_READING, &amp;eb-&gt;bflags))         goto done; At this point, it seems safe to start the actual read operation. Once that completes, end_bbio_meta_read() does     /* (3) */     set_extent_buffer_uptodate(eb);     /* (4) */     clear_bit(EXTENT_BUFFER_READING, &amp;eb-&gt;bflags); 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:     Thread A | Thread B | Thread C     ---------+----------+---------        (1)   |          |              |    (1)   |        (2)   |          |        (3)   |          |        (4)   |          |              |    (2)   |              |          |    (1) 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 result in tr…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2024-35798"/>
  </entry>
</feed>
