<?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://vulnerability.circl.lu</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>Mon, 28 Sep 2026 15:40:34 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-97943</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-97943</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;x86/mm/pat: Acquire init_mm write lock on collapse to avoid UAF&lt;/p&gt;
&lt;p&gt;x86 implements page attribute modification using its Change Page
Attributes (CPA) mechanism.&lt;/p&gt;
&lt;p&gt;This tracks properties of ranges such as cache mode through x86 page
attributes, and as part of that logic manipulates kernel page tables.&lt;/p&gt;
&lt;p&gt;Since commit:&lt;/p&gt;
&lt;p&gt;41d88484c71c (&amp;#34;x86/mm/pat: restore large ROX pages after fragmentation&amp;#34;)&lt;/p&gt;
&lt;p&gt;ranges of kernel page table entries can be collapsed into
huge page table entries as part of this logic.&lt;/p&gt;
&lt;p&gt;As part of this collapse, it frees the page tables which the collapsed
entries previously pointed to, and it does so without any relevant locks
being held to preclude concurrent kernel page table walkers.&lt;/p&gt;
&lt;p&gt;The only way this code can be reached is if CPA_COLLAPSE is specified, and
this is only set in set_memory_rox() via:&lt;/p&gt;
&lt;p&gt;set_memory_rox()
-&amp;gt; change_page_attr_set_clr()
-&amp;gt; cpa_flush()
-&amp;gt; cpa_collapse_large_pages()&lt;/p&gt;
&lt;p&gt;Notable users of this are execmem and BPF when manipulating executable
mappings.&lt;/p&gt;
&lt;p&gt;However, this is problematic for ptdump as it walks ranges it does not own
and thus runs the risk of a use-after-free on page tables freed underneath
it.&lt;/p&gt;
&lt;p&gt;In addition, concurrent CPA collapse operations are possible which can also
cause races.&lt;/p&gt;
&lt;p&gt;Resolve the issue by acquiring the mmap write lock on init_mm across the
whole operation.&lt;/p&gt;
&lt;p&gt;It is safe to acquire a sleeping lock as all the callers invoke
set_memory_rox() from process conte…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;x86/mm/pat: Acquire init_mm write lock on collapse to avoid UAF&lt;/p&gt;
&lt;p&gt;x86 implements page attribute modification using its Change Page
Attributes (CPA) mechanism.&lt;/p&gt;
&lt;p&gt;This tracks properties of ranges such as cache mode through x86 page
attributes, and as part of that logic manipulates kernel page tables.&lt;/p&gt;
&lt;p&gt;Since commit:&lt;/p&gt;
&lt;p&gt;41d88484c71c (&amp;#34;x86/mm/pat: restore large ROX pages after fragmentation&amp;#34;)&lt;/p&gt;
&lt;p&gt;ranges of kernel page table entries can be collapsed into
huge page table entries as part of this logic.&lt;/p&gt;
&lt;p&gt;As part of this collapse, it frees the page tables which the collapsed
entries previously pointed to, and it does so without any relevant locks
being held to preclude concurrent kernel page table walkers.&lt;/p&gt;
&lt;p&gt;The only way this code can be reached is if CPA_COLLAPSE is specified, and
this is only set in set_memory_rox() via:&lt;/p&gt;
&lt;p&gt;set_memory_rox()
-&amp;gt; change_page_attr_set_clr()
-&amp;gt; cpa_flush()
-&amp;gt; cpa_collapse_large_pages()&lt;/p&gt;
&lt;p&gt;Notable users of this are execmem and BPF when manipulating executable
mappings.&lt;/p&gt;
&lt;p&gt;However, this is problematic for ptdump as it walks ranges it does not own
and thus runs the risk of a use-after-free on page tables freed underneath
it.&lt;/p&gt;
&lt;p&gt;In addition, concurrent CPA collapse operations are possible which can also
cause races.&lt;/p&gt;
&lt;p&gt;Resolve the issue by acquiring the mmap write lock on init_mm across the
whole operation.&lt;/p&gt;
&lt;p&gt;It is safe to acquire a sleeping lock as all the callers invoke
set_memory_rox() from process conte…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-97943</guid>
    </item>
    <item>
      <title>GHSA-vv3w-94g3-pv9v</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-vv3w-94g3-pv9v</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;x86/mm/pat: Acquire init_mm write lock on collapse to avoid UAF&lt;/p&gt;
&lt;p&gt;x86 implements page attribute modification using its Change Page
Attributes (CPA) mechanism.&lt;/p&gt;
&lt;p&gt;This tracks properties of ranges such as cache mode through x86 page
attributes, and as part of that logic manipulates kernel page tables.&lt;/p&gt;
&lt;p&gt;Since commit:&lt;/p&gt;
&lt;p&gt;41d88484c71c (&amp;#34;x86/mm/pat: restore large ROX pages after fragmentation&amp;#34;)&lt;/p&gt;
&lt;p&gt;ranges of kernel page table entries can be collapsed into
huge page table entries as part of this logic.&lt;/p&gt;
&lt;p&gt;As part of this collapse, it frees the page tables which the collapsed
entries previously pointed to, and it does so without any relevant locks
being held to preclude concurrent kernel page table walkers.&lt;/p&gt;
&lt;p&gt;The only way this code can be reached is if CPA_COLLAPSE is specified, and
this is only set in set_memory_rox() via:&lt;/p&gt;
&lt;p&gt;set_memory_rox()
-&amp;gt; change_page_attr_set_clr()
-&amp;gt; cpa_flush()
-&amp;gt; cpa_collapse_large_pages()&lt;/p&gt;
&lt;p&gt;Notable users of this are execmem and BPF when manipulating executable
mappings.&lt;/p&gt;
&lt;p&gt;However, this is problematic for ptdump as it walks ranges it does not own
and thus runs the risk of a use-after-free on page tables freed underneath
it.&lt;/p&gt;
&lt;p&gt;In addition, concurrent CPA collapse operations are possible which can also
cause races.&lt;/p&gt;
&lt;p&gt;Resolve the issue by acquiring the mmap write lock on init_mm across the
whole operation.&lt;/p&gt;
&lt;p&gt;It is safe to acquire a sleeping lock as all the callers invoke
set_memory_rox() from process conte…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;x86/mm/pat: Acquire init_mm write lock on collapse to avoid UAF&lt;/p&gt;
&lt;p&gt;x86 implements page attribute modification using its Change Page
Attributes (CPA) mechanism.&lt;/p&gt;
&lt;p&gt;This tracks properties of ranges such as cache mode through x86 page
attributes, and as part of that logic manipulates kernel page tables.&lt;/p&gt;
&lt;p&gt;Since commit:&lt;/p&gt;
&lt;p&gt;41d88484c71c (&amp;#34;x86/mm/pat: restore large ROX pages after fragmentation&amp;#34;)&lt;/p&gt;
&lt;p&gt;ranges of kernel page table entries can be collapsed into
huge page table entries as part of this logic.&lt;/p&gt;
&lt;p&gt;As part of this collapse, it frees the page tables which the collapsed
entries previously pointed to, and it does so without any relevant locks
being held to preclude concurrent kernel page table walkers.&lt;/p&gt;
&lt;p&gt;The only way this code can be reached is if CPA_COLLAPSE is specified, and
this is only set in set_memory_rox() via:&lt;/p&gt;
&lt;p&gt;set_memory_rox()
-&amp;gt; change_page_attr_set_clr()
-&amp;gt; cpa_flush()
-&amp;gt; cpa_collapse_large_pages()&lt;/p&gt;
&lt;p&gt;Notable users of this are execmem and BPF when manipulating executable
mappings.&lt;/p&gt;
&lt;p&gt;However, this is problematic for ptdump as it walks ranges it does not own
and thus runs the risk of a use-after-free on page tables freed underneath
it.&lt;/p&gt;
&lt;p&gt;In addition, concurrent CPA collapse operations are possible which can also
cause races.&lt;/p&gt;
&lt;p&gt;Resolve the issue by acquiring the mmap write lock on init_mm across the
whole operation.&lt;/p&gt;
&lt;p&gt;It is safe to acquire a sleeping lock as all the callers invoke
set_memory_rox() from process conte…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-vv3w-94g3-pv9v</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-97943</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-97943</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: x86/mm/pat: Acquire init_mm write lock on collapse to avoid UAF x86 implements page attribute modification using its Change Page Attributes (CPA) mechanism. This tracks properties of ranges such as cache mode through x86 page attributes, and as part of that logic manipulates kernel page tables. Since commit:   41d88484c71c (&amp;#34;x86/mm/pat: restore large ROX pages after fragmentation&amp;#34;) ranges of kernel page table entries can be collapsed into huge page table entries as part of this logic. As part of this collapse, it frees the page tables which the collapsed entries previously pointed to, and it does so without any relevant locks being held to preclude concurrent kernel page table walkers. The only way this code can be reached is if CPA_COLLAPSE is specified, and this is only set in set_memory_rox() via: set_memory_rox() -&amp;gt; change_page_attr_set_clr() -&amp;gt; cpa_flush() -&amp;gt; cpa_collapse_large_pages() Notable users of this are execmem and BPF when manipulating executable mappings. However, this is problematic for ptdump as it walks ranges it does not own and thus runs the risk of a use-after-free on page tables freed underneath it. In addition, concurrent CPA collapse operations are possible which can also cause races. Resolve the issue by acquiring the mmap write lock on init_mm across the whole operation. It is safe to acquire a sleeping lock as all the callers invoke set_memory_rox() from process context and in any…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: x86/mm/pat: Acquire init_mm write lock on collapse to avoid UAF x86 implements page attribute modification using its Change Page Attributes (CPA) mechanism. This tracks properties of ranges such as cache mode through x86 page attributes, and as part of that logic manipulates kernel page tables. Since commit:   41d88484c71c (&amp;#34;x86/mm/pat: restore large ROX pages after fragmentation&amp;#34;) ranges of kernel page table entries can be collapsed into huge page table entries as part of this logic. As part of this collapse, it frees the page tables which the collapsed entries previously pointed to, and it does so without any relevant locks being held to preclude concurrent kernel page table walkers. The only way this code can be reached is if CPA_COLLAPSE is specified, and this is only set in set_memory_rox() via: set_memory_rox() -&amp;gt; change_page_attr_set_clr() -&amp;gt; cpa_flush() -&amp;gt; cpa_collapse_large_pages() Notable users of this are execmem and BPF when manipulating executable mappings. However, this is problematic for ptdump as it walks ranges it does not own and thus runs the risk of a use-after-free on page tables freed underneath it. In addition, concurrent CPA collapse operations are possible which can also cause races. Resolve the issue by acquiring the mmap write lock on init_mm across the whole operation. It is safe to acquire a sleeping lock as all the callers invoke set_memory_rox() from process context and in any…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-97943</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3579 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579</guid>
    </item>
  </channel>
</rss>
