CVE-2026-31589

A flaw was found in the Linux kernel's memory management. This vulnerability, known as a use-after-free, occurs when the system attempts to access a memory region after it has been released. Specifically, during the unmapping and invalidation of a memory page folio, the system can incorrectly...

SUSE CVE-2026-31589

In the Linux kernel, the following vulnerability has been resolved: mm: call -freefolio directly in foliounmapinvalidate We can only call filemapfreefolio if we have a reference to or hold a lock on the mapping. Otherwise, we've already removed the folio from the mapping so it no longer pins the...

Linux Distros Unpatched Vulnerability : CVE-2026-31589

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - mm: call -freefolio directly in foliounmapinvalidate We can only call filemapfreefolio if we have a reference to or hold a lock on the mapping. Otherwise, we've...

CVE-2026-31589

In the Linux kernel, the following vulnerability has been resolved: mm: call -freefolio directly in foliounmapinvalidate We can only call filemapfreefolio if we have a reference to or hold a lock on the mapping. Otherwise, we've already removed the folio from the mapping so it no longer pins the...

DEBIAN-CVE-2026-31589

In the Linux kernel, the following vulnerability has been resolved: mm: call -freefolio directly in foliounmapinvalidate We can only call filemapfreefolio if we have a reference to or hold a lock on the mapping. Otherwise, we've already removed the folio from the mapping so it no longer pins the...

CVE-2026-31589 mm: call ->free_folio() directly in folio_unmap_invalidate()

In the Linux kernel, the following vulnerability has been resolved: mm: call -freefolio directly in foliounmapinvalidate We can only call filemapfreefolio if we have a reference to or hold a lock on the mapping. Otherwise, we've already removed the folio from the mapping so it no longer pins the...

CVE-2026-31589

In the Linux kernel, the following vulnerability has been resolved: mm: call -freefolio directly in foliounmapinvalidate We can only call filemapfreefolio if we have a reference to or hold a lock on the mapping. Otherwise, we've already removed the folio from the mapping so it no longer pins the...

CVE-2026-31589

The CVE-2026-31589 issue affects the Linux kernel memory management in the mm path related to folio_unmap_invalidate. The vulnerability arises when the system calls free_folio() directly, instead of loading the free_folio function pointer after obtaining a mapping reference or lock, potentially l...

EUVD-2026-25482

In the Linux kernel, the following vulnerability has been resolved: mm: call -freefolio directly in foliounmapinvalidate We can only call filemapfreefolio if we have a reference to or hold a lock on the mapping. Otherwise, we've already removed the folio from the mapping so it no longer pins the...

CVE-2026-31589 mm: call ->free_folio() directly in folio_unmap_invalidate()

In the Linux kernel, the following vulnerability has been resolved: mm: call -freefolio directly in foliounmapinvalidate We can only call filemapfreefolio if we have a reference to or hold a lock on the mapping. Otherwise, we've already removed the folio from the mapping so it no longer pins the...

CVE-2026-31589

In the Linux kernel, the following vulnerability has been resolved: mm: call -freefolio directly in foliounmapinvalidate We can only call filemapfreefolio if we have a reference to or hold a lock on the mapping. Otherwise, we've already removed the folio from the mapping so it no longer pins the...

Linux kernel 安全漏洞

The Linux kernel is the core of the open-source operating system Linux, developed by the Linux Foundation in the United States. There is a security vulnerability in the Linux kernel, which stems from the fact that the functionfoliounmapinvalidate calls filemapfreefolio without holding a reference...

kernel: Linux kernel: Denial of Service due to a deadlock in hugetlb folio migration

A flaw was found in the Linux kernel. A local attacker could exploit a deadlock vulnerability due to incorrect lock ordering between foliolock and immaprwsem when migrating hugetlb file-backed folios. This could lead to hung tasks and potential system-wide stalls, resulting in a Denial of Service...

ext4: replace BUG_ON with proper error handling in ext4_read_inline_folio

...

SUSE CVE-2026-31463

In the Linux kernel, the following vulnerability has been resolved: iomap: fix invalid folio access when iblkbits differs from I/O granularity Commit aa35dd5cbc06 "iomap: fix invalid folio access after folioendread" partially addressed invalid folio access for folios without an ifs attached, but ...

SUSE CVE-2026-31466

In the Linux kernel, the following vulnerability has been resolved: mm/hugememory: fix folio isn't locked in softleaftofolio On arm64 server, we found folio that get from migration entry isn't locked in softleaftofolio. This issue triggers when mTHP splitting and zapnonpresentptes races, and the...

CVE-2026-31463

A flaw was found in the Linux kernel's iomap subsystem. This vulnerability occurs when the block size of an inode iblkbits differs from the granularity used for input/output I/O operations. This mismatch can lead to invalid access of data pages folios during read operations, potentially causing...

EUVD-2026-24811

In the Linux kernel, the following vulnerability has been resolved: mm/hugememory: fix folio isn't locked in softleaftofolio On arm64 server, we found folio that get from migration entry isn't locked in softleaftofolio. This issue triggers when mTHP splitting and zapnonpresentptes races, and the...

EUVD-2026-24805

In the Linux kernel, the following vulnerability has been resolved: iomap: fix invalid folio access when iblkbits differs from I/O granularity Commit aa35dd5cbc06 "iomap: fix invalid folio access after folioendread" partially addressed invalid folio access for folios without an ifs attached, but ...

CVE-2026-31463

In the Linux kernel, the following vulnerability has been resolved: iomap: fix invalid folio access when iblkbits differs from I/O granularity Commit aa35dd5cbc06 "iomap: fix invalid folio access after folioendread" partially addressed invalid folio access for folios without an ifs attached, but ...