<?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-20T23:42:40.313055+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-2025-38626</id>
    <title>BELL-CVE-2025-38626</title>
    <updated>2026-11-20T23:42:40.327925+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/bell-cve-2025-38626"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2025-avi-1050</id>
    <title>certfr-2025-avi-1050 — 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-20T23:42:40.327967+00:00</updated>
    <content>certfr-2025-avi-1050</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2025-avi-1050"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38626</id>
    <title>UBUNTU-CVE-2025-38626</title>
    <updated>2026-11-20T23:42:40.327983+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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 216 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to trigger foreground gc during f2fs_map_blocks() in lfs mode w/ "mode=lfs" mount option, generic/299 will cause system panic as below: ------------[ cut here ]------------ kernel BUG at fs/f2fs/segment.c:2835! Call Trace:  &lt;TASK&gt;  f2fs_allocate_data_block+0x6f4/0xc50  f2fs_map_blocks+0x970/0x1550  f2fs_iomap_begin+0xb2/0x1e0  iomap_iter+0x1d6/0x430  __iomap_dio_rw+0x208/0x9a0  f2fs_file_write_iter+0x6b3/0xfa0  aio_write+0x15d/0x2e0  io_submit_one+0x55e/0xab0  __x64_sys_io_submit+0xa5/0x230  do_syscall_64+0x84/0x2f0  entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0010:new_curseg+0x70f/0x720 The root cause of we run out-of-space is: in f2fs_map_blocks(), f2fs may trigger foreground gc only if it allocates any physical block, it will be a little bit later when there is multiple threads writing data w/ aio/dio/bufio method in parallel, since we always use OPU in lfs mode, so f2fs_map_blocks() does block allocations aggressively. In order to fix this issue, let's give a chance to trigger foreground gc in prior to block allocation in f2fs_map_blocks().</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38626"/>
  </entry>
</feed>
