<?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-19T19:37:49.871135+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-2023-52737</id>
    <title>BELL-CVE-2023-52737</title>
    <updated>2026-11-19T19:37:49.886525+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/bell-cve-2023-52737"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2024-avi-0578</id>
    <title>certfr-2024-avi-0578 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
    <updated>2026-11-19T19:37:49.886597+00:00</updated>
    <content>certfr-2024-avi-0578</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2024-avi-0578"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2023-52737</id>
    <title>UBUNTU-CVE-2023-52737</title>
    <updated>2026-11-19T19:37:49.886618+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 98 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: btrfs: lock the inode in shared mode before starting fiemap Currently fiemap does not take the inode's lock (VFS lock), it only locks a file range in the inode's io tree. This however can lead to a deadlock if we have a concurrent fsync on the file and fiemap code triggers a fault when accessing the user space buffer with fiemap_fill_next_extent(). The deadlock happens on the inode's i_mmap_lock semaphore, which is taken both by fsync and btrfs_page_mkwrite(). This deadlock was recently reported by syzbot and triggers a trace like the following:    task:syz-executor361 state:D stack:20264 pid:5668  ppid:5119 flags:0x00004004    Call Trace:     &lt;TASK&gt;     context_switch kernel/sched/core.c:5293 [inline]     __schedule+0x995/0xe20 kernel/sched/core.c:6606     schedule+0xcb/0x190 kernel/sched/core.c:6682     wait_on_state fs/btrfs/extent-io-tree.c:707 [inline]     wait_extent_bit+0x577/0x6f0 fs/btrfs/extent-io-tree.c:751     lock_extent+0x1c2/0x280 fs/btrfs/extent-io-tree.c:1742     find_lock_delalloc_range+0x4e6/0x9c0 fs/btrfs/extent_io.c:488     writepage_delalloc+0x1ef/0x540 fs/btrfs/extent_io.c:1863     __extent_writepage+0x736/0x14e0 fs/btrfs/extent_io.c:2174     extent_write_cache_pages+0x983/0x1220 fs/btrfs/extent_io.c:3091     extent_writepages+0x219/0x540 fs/btrfs/extent_io.c:3211     do_writepages+0x3c3/0x680 mm/page-writeback.c:2581     filemap_fdatawrite_wbc+0x11e/0x170 mm/filemap.c:388     __filema…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2023-52737"/>
  </entry>
</feed>
