<?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:46:18 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-37964</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-37964</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2025-37964</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0464 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0464</link>
      <description>certfr-2025-avi-0464</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0464</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-37964</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-37964</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 117 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: x86/mm: Eliminate window where TLB flushes may be inadvertently skipped tl;dr: There is a window in the mm switching code where the new CR3 is set and the CPU should be getting TLB flushes for the new mm.  But should_flush_tlb() has a bug and suppresses the flush.  Fix it by widening the window where should_flush_tlb() sends an IPI. Long Version: === History === There were a few things leading up to this. First, updating mm_cpumask() was observed to be too expensive, so it was made lazier.  But being lazy caused too many unnecessary IPIs to CPUs due to the now-lazy mm_cpumask().  So code was added to cull mm_cpumask() periodically[2].  But that culling was a bit too aggressive and skipped sending TLB flushes to CPUs that need them.  So here we are again. === Problem === The too-aggressive code in should_flush_tlb() strikes in this window: 	// Turn on IPIs for this CPU/mm combination, but only 	// if should_flush_tlb() agrees: 	cpumask_set_cpu(cpu, mm_cpumask(next)); 	next_tlb_gen = atomic64_read(&amp;amp;next-&amp;gt;context.tlb_gen); 	choose_new_asid(next, next_tlb_gen, &amp;amp;new_asid, &amp;amp;need_flush); 	load_new_mm_cr3(need_flush); 	// ^ After &amp;#39;need_flush&amp;#39; is set to false, IPIs *MUST* 	// be sent to this CPU and not be ignored.         this_cpu_write(cpu_tlbstate.loaded_mm, next); 	// ^ Not until this point does should_flush_tlb() 	// become true! should_flush_tlb() will suppress TLB flushes between load_new_mm_cr3() and writing…&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 117 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: x86/mm: Eliminate window where TLB flushes may be inadvertently skipped tl;dr: There is a window in the mm switching code where the new CR3 is set and the CPU should be getting TLB flushes for the new mm.  But should_flush_tlb() has a bug and suppresses the flush.  Fix it by widening the window where should_flush_tlb() sends an IPI. Long Version: === History === There were a few things leading up to this. First, updating mm_cpumask() was observed to be too expensive, so it was made lazier.  But being lazy caused too many unnecessary IPIs to CPUs due to the now-lazy mm_cpumask().  So code was added to cull mm_cpumask() periodically[2].  But that culling was a bit too aggressive and skipped sending TLB flushes to CPUs that need them.  So here we are again. === Problem === The too-aggressive code in should_flush_tlb() strikes in this window: 	// Turn on IPIs for this CPU/mm combination, but only 	// if should_flush_tlb() agrees: 	cpumask_set_cpu(cpu, mm_cpumask(next)); 	next_tlb_gen = atomic64_read(&amp;amp;next-&amp;gt;context.tlb_gen); 	choose_new_asid(next, next_tlb_gen, &amp;amp;new_asid, &amp;amp;need_flush); 	load_new_mm_cr3(need_flush); 	// ^ After &amp;#39;need_flush&amp;#39; is set to false, IPIs *MUST* 	// be sent to this CPU and not be ignored.         this_cpu_write(cpu_tlbstate.loaded_mm, next); 	// ^ Not until this point does should_flush_tlb() 	// become true! should_flush_tlb() will suppress TLB flushes between load_new_mm_cr3() and writing…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-37964</guid>
    </item>
  </channel>
</rss>
