kernel: gfs2: Fix use-after-free in iomap inline data write path

A flaw was found in the Linux kernel's GFS2 filesystem. This memory corruption vulnerability, a use-after-free, occurs in the iomap inline data write path. The issue arises because a data buffer is released prematurely while still being referenced, leading to a write to freed memory. This could...

PT-2026-69545

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description An out-of-bounds write occurs in the iomap subsystem when handling zero-length ranges. The functions ifs set range dirty and ifs set range uptodate calculate the last blk value using a...

RHEL 9 : kernel-rt (RHSA-2026:51604)

The remote Redhat Enterprise Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2026:51604 advisory. The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism...

RockyLinux 9 : kernel (RLSA-2026:27789)

The remote RockyLinux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RLSA-2026:27789 advisory. kernel: can: isotp: fix tx.buf use-after-free in isotpsendmsg CVE-2026-31474 kernel: mptcp: fix slab-use-after-free in inetlookupestablished...

EUVD-2025-2616

Malicious code in bioql PyPI...

The vulnerability of the iomap_write_delalloc_scan() function in Linux operating systems allows a hacker to trigger a service failure.

The vulnerability of the iomapwritedelallocscan function in Linux operating systems is related to the execution of a loop with an unreachable exit condition due to numerical truncation. Exploiting this vulnerability can allow an attacker to cause a service failure...

CVE-2025-21667 iomap: avoid avoid truncating 64-bit offset to 32 bits

In the Linux kernel, the following vulnerability has been resolved: iomap: avoid avoid truncating 64-bit offset to 32 bits on 32-bit kernels, iomapwritedelallocscan was inadvertently using a 32-bit position due to folionextindex returning an unsigned long. This could lead to an infinite loop when...