<?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>Sat, 21 Nov 2026 03:47:43 +0000</lastBuildDate>
    <item>
      <title>Withdrawn: BELL-CVE-2026-53165 — CVE-2026-53165 does not affect BellSoft software</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-53165</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2026-53165</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1162 — 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-1162</link>
      <description>certfr-2026-avi-1162</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-1162</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-53165</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-53165</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 110 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: iomap: avoid potential null folio-&amp;gt;mapping deref during error reporting When a buffered read fails, iomap_finish_folio_read() reports the error with fserror_report_io(folio-&amp;gt;mapping-&amp;gt;host, ...). This is called after ifs-&amp;gt;read_bytes_pending has been decremented by the bytes attempted to be read. For a folio split across multiple read completions, the folio is only guaranteed to stay locked while read_bytes_pending &amp;gt; 0. Once iomap_finish_folio_read() decrements read_bytes_pending, another in-flight read can complete and end the read on the folio, which unlocks it. This allows truncate logic to run and detach the folio (set folio-&amp;gt;mapping to NULL). The error reporting path then can dereference a NULL folio-&amp;gt;mapping. As reported by Sam Sun, this is the race that can occur: CPU0: failed completion      CPU1: final completion     CPU2: truncate -----------------------      ----------------------     -------------- read_bytes_pending -= len finished = false /* preempted before    fserror_report_io() */ 			     read_bytes_pending -= len 			     finished = true 			     folio_end_read() 							truncate clears 							folio-&amp;gt;mapping fserror_report_io(   folio-&amp;gt;mapping-&amp;gt;host, ...) 	      ^ NULL deref Fix this by reporting the error first before decrementing ifs-&amp;gt;read_bytes_pending.&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 110 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: iomap: avoid potential null folio-&amp;gt;mapping deref during error reporting When a buffered read fails, iomap_finish_folio_read() reports the error with fserror_report_io(folio-&amp;gt;mapping-&amp;gt;host, ...). This is called after ifs-&amp;gt;read_bytes_pending has been decremented by the bytes attempted to be read. For a folio split across multiple read completions, the folio is only guaranteed to stay locked while read_bytes_pending &amp;gt; 0. Once iomap_finish_folio_read() decrements read_bytes_pending, another in-flight read can complete and end the read on the folio, which unlocks it. This allows truncate logic to run and detach the folio (set folio-&amp;gt;mapping to NULL). The error reporting path then can dereference a NULL folio-&amp;gt;mapping. As reported by Sam Sun, this is the race that can occur: CPU0: failed completion      CPU1: final completion     CPU2: truncate -----------------------      ----------------------     -------------- read_bytes_pending -= len finished = false /* preempted before    fserror_report_io() */ 			     read_bytes_pending -= len 			     finished = true 			     folio_end_read() 							truncate clears 							folio-&amp;gt;mapping fserror_report_io(   folio-&amp;gt;mapping-&amp;gt;host, ...) 	      ^ NULL deref Fix this by reporting the error first before decrementing ifs-&amp;gt;read_bytes_pending.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-53165</guid>
    </item>
  </channel>
</rss>
