Most recent entries from all

Most recent entries from all https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 28 Sep 2026 19:00:48 +0000 fkie_cve-2026-97533 https://vulnerability.circl.lu/vuln/fkie_cve-2026-97533 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>x86/mm/pat: Acquire init_mm read lock on attribute changes to avoid UAF</p> <p>A previous commit protected against races between ptdump and CPA collapse, however one still exists between attribute changes and collapse as reported by Denis V. Lunev (linked).</p> <p>When an attribute change arises, a lockless page table walker obtains a PTE entry, which is later written to via set_pte_atomic():</p> <p>... -> change_page_attr_set_clr() -> __change_page_attr_set_clr() -> __change_page_attr() -> _lookup_address_cpa() -> lookup_address_in_pgd_attr() -> [ lockless page table walker ] -> set_pte_atomic()</p> <p>There is nothing preventing a concurrent CPA collapse which can free the PTE that was retrieved here, resulting in a use-after-free.</p> <p>With the mmap write lock taken on init_mm over CPA collapse, resolve this race by acquiring an mmap read lock on init_mm over __change_page_attr_set_clr().</p> <p>This locks across the whole operation over which the walk and the PTE entry write occurs, solving the race.</p> <p>It is safe to do this here, as no spinlocks are held upon entry to __change_page_attr_set_clr().</p> <p>However, the lock must not be held over an allocation, as allocation can trigger reclaim and shrinkers may call into CPA recursively, making deadlocks possible (init_mm -> ... -> fs_reclaim -> init_mm).</p> <p>A page table is allocated when a huge page needs to be split:</p> <p>-> change_page_attr_set_clr() -> __change_page_attr_set_clr()…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>x86/mm/pat: Acquire init_mm read lock on attribute changes to avoid UAF</p> <p>A previous commit protected against races between ptdump and CPA collapse, however one still exists between attribute changes and collapse as reported by Denis V. Lunev (linked).</p> <p>When an attribute change arises, a lockless page table walker obtains a PTE entry, which is later written to via set_pte_atomic():</p> <p>... -> change_page_attr_set_clr() -> __change_page_attr_set_clr() -> __change_page_attr() -> _lookup_address_cpa() -> lookup_address_in_pgd_attr() -> [ lockless page table walker ] -> set_pte_atomic()</p> <p>There is nothing preventing a concurrent CPA collapse which can free the PTE that was retrieved here, resulting in a use-after-free.</p> <p>With the mmap write lock taken on init_mm over CPA collapse, resolve this race by acquiring an mmap read lock on init_mm over __change_page_attr_set_clr().</p> <p>This locks across the whole operation over which the walk and the PTE entry write occurs, solving the race.</p> <p>It is safe to do this here, as no spinlocks are held upon entry to __change_page_attr_set_clr().</p> <p>However, the lock must not be held over an allocation, as allocation can trigger reclaim and shrinkers may call into CPA recursively, making deadlocks possible (init_mm -> ... -> fs_reclaim -> init_mm).</p> <p>A page table is allocated when a huge page needs to be split:</p> <p>-> change_page_attr_set_clr() -> __change_page_attr_set_clr()…</p> https://vulnerability.circl.lu/vuln/fkie_cve-2026-97533 GHSA-4g49-6xf9-67qq https://vulnerability.circl.lu/vuln/ghsa-4g49-6xf9-67qq <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>x86/mm/pat: Acquire init_mm read lock on attribute changes to avoid UAF</p> <p>A previous commit protected against races between ptdump and CPA collapse, however one still exists between attribute changes and collapse as reported by Denis V. Lunev (linked).</p> <p>When an attribute change arises, a lockless page table walker obtains a PTE entry, which is later written to via set_pte_atomic():</p> <p>... -> change_page_attr_set_clr() -> __change_page_attr_set_clr() -> __change_page_attr() -> _lookup_address_cpa() -> lookup_address_in_pgd_attr() -> [ lockless page table walker ] -> set_pte_atomic()</p> <p>There is nothing preventing a concurrent CPA collapse which can free the PTE that was retrieved here, resulting in a use-after-free.</p> <p>With the mmap write lock taken on init_mm over CPA collapse, resolve this race by acquiring an mmap read lock on init_mm over __change_page_attr_set_clr().</p> <p>This locks across the whole operation over which the walk and the PTE entry write occurs, solving the race.</p> <p>It is safe to do this here, as no spinlocks are held upon entry to __change_page_attr_set_clr().</p> <p>However, the lock must not be held over an allocation, as allocation can trigger reclaim and shrinkers may call into CPA recursively, making deadlocks possible (init_mm -> ... -> fs_reclaim -> init_mm).</p> <p>A page table is allocated when a huge page needs to be split:</p> <p>-> change_page_attr_set_clr() -> __change_page_attr_set_clr()…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>x86/mm/pat: Acquire init_mm read lock on attribute changes to avoid UAF</p> <p>A previous commit protected against races between ptdump and CPA collapse, however one still exists between attribute changes and collapse as reported by Denis V. Lunev (linked).</p> <p>When an attribute change arises, a lockless page table walker obtains a PTE entry, which is later written to via set_pte_atomic():</p> <p>... -> change_page_attr_set_clr() -> __change_page_attr_set_clr() -> __change_page_attr() -> _lookup_address_cpa() -> lookup_address_in_pgd_attr() -> [ lockless page table walker ] -> set_pte_atomic()</p> <p>There is nothing preventing a concurrent CPA collapse which can free the PTE that was retrieved here, resulting in a use-after-free.</p> <p>With the mmap write lock taken on init_mm over CPA collapse, resolve this race by acquiring an mmap read lock on init_mm over __change_page_attr_set_clr().</p> <p>This locks across the whole operation over which the walk and the PTE entry write occurs, solving the race.</p> <p>It is safe to do this here, as no spinlocks are held upon entry to __change_page_attr_set_clr().</p> <p>However, the lock must not be held over an allocation, as allocation can trigger reclaim and shrinkers may call into CPA recursively, making deadlocks possible (init_mm -> ... -> fs_reclaim -> init_mm).</p> <p>A page table is allocated when a huge page needs to be split:</p> <p>-> change_page_attr_set_clr() -> __change_page_attr_set_clr()…</p> https://vulnerability.circl.lu/vuln/ghsa-4g49-6xf9-67qq UBUNTU-CVE-2026-97533 https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-97533 <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 246 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: x86/mm/pat: Acquire init_mm read lock on attribute changes to avoid UAF A previous commit protected against races between ptdump and CPA collapse, however one still exists between attribute changes and collapse as reported by Denis V. Lunev (linked). When an attribute change arises, a lockless page table walker obtains a PTE entry, which is later written to via set_pte_atomic(): ... -> change_page_attr_set_clr() -> __change_page_attr_set_clr() -> __change_page_attr() -> _lookup_address_cpa() -> lookup_address_in_pgd_attr() -> [ lockless page table walker ] -> set_pte_atomic() There is nothing preventing a concurrent CPA collapse which can free the PTE that was retrieved here, resulting in a use-after-free. With the mmap write lock taken on init_mm over CPA collapse, resolve this race by acquiring an mmap read lock on init_mm over __change_page_attr_set_clr(). This locks across the whole operation over which the walk and the PTE entry write occurs, solving the race. It is safe to do this here, as no spinlocks are held upon entry to __change_page_attr_set_clr(). However, the lock must not be held over an allocation, as allocation can trigger reclaim and shrinkers may call into CPA recursively, making deadlocks possible (init_mm -> ... -> fs_reclaim -> init_mm). A page table is allocated when a huge page needs to be split: -> change_page_attr_set_clr() -> __change_page_attr_set_clr() -> __cha…</p> <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 246 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: x86/mm/pat: Acquire init_mm read lock on attribute changes to avoid UAF A previous commit protected against races between ptdump and CPA collapse, however one still exists between attribute changes and collapse as reported by Denis V. Lunev (linked). When an attribute change arises, a lockless page table walker obtains a PTE entry, which is later written to via set_pte_atomic(): ... -> change_page_attr_set_clr() -> __change_page_attr_set_clr() -> __change_page_attr() -> _lookup_address_cpa() -> lookup_address_in_pgd_attr() -> [ lockless page table walker ] -> set_pte_atomic() There is nothing preventing a concurrent CPA collapse which can free the PTE that was retrieved here, resulting in a use-after-free. With the mmap write lock taken on init_mm over CPA collapse, resolve this race by acquiring an mmap read lock on init_mm over __change_page_attr_set_clr(). This locks across the whole operation over which the walk and the PTE entry write occurs, solving the race. It is safe to do this here, as no spinlocks are held upon entry to __change_page_attr_set_clr(). However, the lock must not be held over an allocation, as allocation can trigger reclaim and shrinkers may call into CPA recursively, making deadlocks possible (init_mm -> ... -> fs_reclaim -> init_mm). A page table is allocated when a huge page needs to be split: -> change_page_attr_set_clr() -> __change_page_attr_set_clr() -> __cha…</p> https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-97533 WID-SEC-W-2026-3579 — Linux Kernel: Mehrere Schwachstellen https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579 <p>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.</p> <p>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.</p> https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579