<?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://127.0.0.1:10001</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>Fri, 20 Nov 2026 23:34:56 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-71201</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-71201</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2025-71201</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0926 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-0926</link>
      <description>certfr-2026-avi-0926</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0926</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-71201</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-71201</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 106 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: netfs: Fix early read unlock of page with EOF in middle The read result collection for buffered reads seems to run ahead of the completion of subrequests under some circumstances, as can be seen in the following log snippet:     9p_client_res: client 18446612686390831168 response P9_TREAD tag  0 err 0     ...     netfs_sreq: R=00001b55[1] DOWN TERM  f=192 s=0 5fb2/5fb2 s=5 e=0     ...     netfs_collect_folio: R=00001b55 ix=00004 r=4000-5000 t=4000/5fb2     netfs_folio: i=157f3 ix=00004-00004 read-done     netfs_folio: i=157f3 ix=00004-00004 read-unlock     netfs_collect_folio: R=00001b55 ix=00005 r=5000-5fb2 t=5000/5fb2     netfs_folio: i=157f3 ix=00005-00005 read-done     netfs_folio: i=157f3 ix=00005-00005 read-unlock     ...     netfs_collect_stream: R=00001b55[0:] cto=5fb2 frn=ffffffff     netfs_collect_state: R=00001b55 col=5fb2 cln=6000 n=c     netfs_collect_stream: R=00001b55[0:] cto=5fb2 frn=ffffffff     netfs_collect_state: R=00001b55 col=5fb2 cln=6000 n=8     ...     netfs_sreq: R=00001b55[2] ZERO SUBMT f=000 s=5fb2 0/4e s=0 e=0     netfs_sreq: R=00001b55[2] ZERO TERM  f=102 s=5fb2 4e/4e s=5 e=0 The &amp;#39;cto=5fb2&amp;#39; indicates the collected file pos we&amp;#39;ve collected results to so far - but we still have 0x4e more bytes to go - so we shouldn&amp;#39;t have collected folio ix=00005 yet.  The &amp;#39;ZERO&amp;#39; subreq that clears the tail happens after we unlock the folio, allowing the application to see the uncleared tail throu…&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 106 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: netfs: Fix early read unlock of page with EOF in middle The read result collection for buffered reads seems to run ahead of the completion of subrequests under some circumstances, as can be seen in the following log snippet:     9p_client_res: client 18446612686390831168 response P9_TREAD tag  0 err 0     ...     netfs_sreq: R=00001b55[1] DOWN TERM  f=192 s=0 5fb2/5fb2 s=5 e=0     ...     netfs_collect_folio: R=00001b55 ix=00004 r=4000-5000 t=4000/5fb2     netfs_folio: i=157f3 ix=00004-00004 read-done     netfs_folio: i=157f3 ix=00004-00004 read-unlock     netfs_collect_folio: R=00001b55 ix=00005 r=5000-5fb2 t=5000/5fb2     netfs_folio: i=157f3 ix=00005-00005 read-done     netfs_folio: i=157f3 ix=00005-00005 read-unlock     ...     netfs_collect_stream: R=00001b55[0:] cto=5fb2 frn=ffffffff     netfs_collect_state: R=00001b55 col=5fb2 cln=6000 n=c     netfs_collect_stream: R=00001b55[0:] cto=5fb2 frn=ffffffff     netfs_collect_state: R=00001b55 col=5fb2 cln=6000 n=8     ...     netfs_sreq: R=00001b55[2] ZERO SUBMT f=000 s=5fb2 0/4e s=0 e=0     netfs_sreq: R=00001b55[2] ZERO TERM  f=102 s=5fb2 4e/4e s=5 e=0 The &amp;#39;cto=5fb2&amp;#39; indicates the collected file pos we&amp;#39;ve collected results to so far - but we still have 0x4e more bytes to go - so we shouldn&amp;#39;t have collected folio ix=00005 yet.  The &amp;#39;ZERO&amp;#39; subreq that clears the tail happens after we unlock the folio, allowing the application to see the uncleared tail throu…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-71201</guid>
    </item>
  </channel>
</rss>
