CVE-2026-74362

A flaw was found in the Linux kernel's ext2 filesystem. When performing write operations on files opened with OSYNC or ODSYNC flags, the system call write2 could incorrectly report success to a local user even if the data synchronization to disk failed. This could lead to data integrity issues, a...

Linux Distros Unpatched Vulnerability : CVE-2026-74362

"The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - ext2: fix ignored return value of genericwritesync Fix ext2diowriteiter to propagate the error returned by genericwritesync instead of silently discarding it,...

CVE-2026-74362 ext2: fix ignored return value of generic_write_sync()

In the Linux kernel, the following vulnerability has been resolved: ext2: fix ignored return value of genericwritesync Fix ext2diowriteiter to propagate the error returned by genericwritesync instead of silently discarding it, which could cause write2 to return success to userspace on OSYNC/ODSYN...

PT-2026-72798

In the Linux kernel, the following vulnerability has been resolved: ext2: fix ignored return value of generic write sync Fix ext2 dio write iter to propagate the error returned by generic write sync instead of silently discarding it, which could cause write2 to return success to userspace on O...

CVE-2026-7007

The Zephyr ext2 file system validates the on-disk superblock in ext2verifydisksuperblock subsys/fs/ext2/ext2impl.c before completing a mount. The validator checked the magic number, block size, revision and feature flags, but did not verify that the on-disk fields sblockspergroup and...

PT-2026-64305

Name of the Vulnerable Software and Affected Versions Zephyr affected versions not specified Description The ext2 file system fails to verify that the on-disk superblock fields s blocks per group and s inodes per group are non-zero during the mount process in the ext2 verify disk superblock...

CVE-2026-53129

In the Linux kernel, the following vulnerability has been resolved: fs/mbcache: cancel shrink work before destroying the cache mbcachedestroy calls shrinkerfree and then frees all cache entries and the cache itself, but it does not cancel the pending cshrinkwork work item first. If...

CVE-2026-46002

Summary (CVE-2026-46002) The Linux kernel ext2 inode handling is fixed to catch a corner case where an inode with i_nlink == 0 and a non-zero i_mode could slip through if i_dtime is 0, allowing a crafted image to trigger WARN_ON in drop_nlink() via ext2_unlink/rename/rmdir. The patch extends the ...

EUVD-2026-32298

In the Linux kernel, the following vulnerability has been resolved: ext2: reject inodes with zero inlink and valid mode in ext2iget ext2iget already rejects inodes with inlink == 0 when imode is zero or idtime is set, treating them as deleted. However, the case of inlink == 0 with a non-zero mode...

CVE-2026-46002

In the Linux kernel, the following vulnerability has been resolved: ext2: reject inodes with zero inlink and valid mode in ext2iget ext2iget already rejects inodes with inlink == 0 when imode is zero or idtime is set, treating them as deleted. However, the case of inlink == 0 with a non-zero mode...

PT-2026-43869

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description An issue exists in the ext2 filesystem where the ext2 iget function fails to reject inodes that have a link count i nlink of zero while maintaining a valid mode and a zero deletion time ...

kernel: Fix of 10 CVEs

ACPICA: Add AMLNOOPERANDRESOLVE flag to Timer CVE-2023-53395 - net: ppp: Add bound checking for skb data on pppsynctxmung CVE-2025-37749 - ata: ahci: Match EMMAXSLOTS with SATAPMPMAXPORTS CVE-2022-50315 - ext2: Check block size validity during mount CVE-2023-53569 - gfs2: Fix possible data races...

CLSA-2026-1773044010 kernel: Fix of 10 CVEs

ACPICA: Add AMLNOOPERANDRESOLVE flag to Timer CVE-2023-53395 - net: ppp: Add bound checking for skb data on pppsynctxmung CVE-2025-37749 - ata: ahci: Match EMMAXSLOTS with SATAPMPMAXPORTS CVE-2022-50315 - ext2: Check block size validity during mount CVE-2023-53569 - gfs2: Fix possible data races...

SUSE CVE-2022-50815

In the Linux kernel, the following vulnerability has been resolved: ext2: Add sanity checks for group and filesystem size Add sanity check that filesystem size does not exceed the underlying device size and that group size is big enough so that metadata can fit into it. This avoid trying to mount...

CVE-2022-50815

In the Linux kernel, the following vulnerability has been resolved: ext2: Add sanity checks for group and filesystem size Add sanity check that filesystem size does not exceed the underlying device size and that group size is big enough so that metadata can fit into it. This avoid trying to mount...

UBUNTU-CVE-2022-50815

In the Linux kernel, the following vulnerability has been resolved: ext2: Add sanity checks for group and filesystem size Add sanity check that filesystem size does not exceed the underlying device size and that group size is big enough so that metadata can fit into it. This avoid trying to mount...

EUVD-2015-8808

Malware in sbrugna...

CVE-2023-53569

The CVE-2023-53569 entry refers to the Linux kernel ext2 filesystem check during mount, where the log of the block size stored in the superblock must be validated to prevent an overflow in the block size calculation. This vulnerability can cause undefined behavior if the block size value is not s...

CVE-2023-53569 ext2: Check block size validity during mount

In the Linux kernel, the following vulnerability has been resolved: ext2: Check block size validity during mount Check that log of block size stored in the superblock has sensible value. Otherwise the shift computing the block size can overflow leading to undefined behavior...

PT-2025-40711

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description A flaw exists in the Linux kernel's ext2 functionality related to block size validity during mount operations. Insufficient validation of the block size log stored in the superblock coul...