Lucene search
+L

4354 matches found

RedhatCVE
RedhatCVE
•added 2026/05/06 3:12 p.m.•28 views

CVE-2026-43076

A flaw was found in the ocfs2 filesystem module of the Linux kernel. This vulnerability occurs when the system attempts to read an inode from a corrupted filesystem, where the inline data size is not properly validated. This can lead to a use-after-free condition, potentially allowing a local...

7.8CVSS7.7AI score0.00131EPSS
SaveExploits0References4
EUVD
EUVD
•added 2026/05/06 12:30 p.m.•24 views

EUVD-2025-209678

In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: handle attrsetsize errors when truncating files If attrsetsize fails while truncating down, the error is silently ignored and the inode may be left in an inconsistent state...

6.4AI score0.00261EPSS
SaveExploits0References3
EUVD
EUVD
•added 2026/05/06 12:30 p.m.•22 views

EUVD-2026-27645

In the Linux kernel, the following vulnerability has been resolved: btrfs: fix zero size inode with non-zero size after log replay When logging that an inode exists, as part of logging a new name or logging new dir entries for a directory, we always set the generation of the logged inode item to ...

5.8AI score0.00156EPSS
SaveExploits0References4
EUVD
EUVD
•added 2026/05/06 12:30 p.m.•26 views

EUVD-2026-27563

In the Linux kernel, the following vulnerability has been resolved: ocfs2: validate inline data isize during inode read When reading an inode from disk, ocfs2validateinodeblock performs various sanity checks but does not validate the size of inline data. If the filesystem is corrupted, an inode's...

7.5AI score0.00131EPSS
SaveExploits0References6
EUVD
EUVD
•added 2026/05/06 12:30 p.m.•30 views

EUVD-2026-27560

In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix out-of-bounds write in ocfs2writeendinline KASAN reports a use-after-free write of 4086 bytes in ocfs2writeendinline, called from ocfs2writeendnolock during a copyfilerange splice fallback on a corrupted ocfs2 filesyst...

7.3AI score0.00126EPSS
SaveExploits0References6
NVD
NVD
•added 2026/05/06 12:16 p.m.•25 views

CVE-2025-71289

In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: handle attrsetsize errors when truncating files If attrsetsize fails while truncating down, the error is silently ignored and the inode may be left in an inconsistent state...

7.1CVSS0.00261EPSS
SaveExploits0References6
Cvelist
Cvelist
•added 2026/05/06 11:32 a.m.•57 views

CVE-2025-71289 fs/ntfs3: handle attr_set_size() errors when truncating files

In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: handle attrsetsize errors when truncating files If attrsetsize fails while truncating down, the error is silently ignored and the inode may be left in an inconsistent state...

7.1CVSS0.00261EPSS
SaveExploits0References6
osv_cve
osv_cve
•added 2026/05/06 11:32 a.m.•28 views

CVE-2025-71289 fs/ntfs3: handle attr_set_size() errors when truncating files

In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: handle attrsetsize errors when truncating files If attrsetsize fails while truncating down, the error is silently ignored and the inode may be left in an inconsistent state...

7.1CVSS5.8AI score0.00261EPSS
SaveExploits0References9
attackerkb
attackerkb
•added 2026/05/06 11:32 a.m.•20 views

CVE-2025-71289

In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: handle attrsetsize errors when truncating files If attrsetsize fails while truncating down, the error is silently ignored and the inode may be left in an inconsistent state...

6.4AI score0.00261EPSS
SaveExploits0References3Affected Software1
CVE
CVE
•added 2026/05/06 11:32 a.m.•64 views

CVE-2025-71289

CVE-2025-71289 affects the Linux kernel’s ntfs3 handling of attr_set_size() when truncating files. If attr_set_size() fails during down-truncation, the error may be silently ignored, potentially leaving the inode in an inconsistent state. The connected sources corroborate this description and lis...

7.1CVSS6.4AI score0.00261EPSS
SaveExploits0References6Affected Software1
osv_cve
osv_cve
•added 2026/05/06 11:28 a.m.•21 views

CVE-2026-43268 hfsplus: pretend special inodes as regular files

In the Linux kernel, the following vulnerability has been resolved: hfsplus: pretend special inodes as regular files Since commit af153bb63a33 "vfs: catch invalid modes in mayopen" requires any inode be one of SIFDIR/SIFLNK/SIFREG/SIFCHR/SIFBLK/ SIFIFO/SIFSOCK type, use SIFREG for special inodes...

6AI score
SaveExploits0References11
attackerkb
attackerkb
•added 2026/05/06 11:28 a.m.•19 views

CVE-2026-43262

In the Linux kernel, the following vulnerability has been resolved: gfs2: fiemap page fault fix In gfs2fiemap, we are calling iomapfiemap while holding the inode glock. This can lead to recursive glock taking if the fiemap buffer is memory mapped to the same inode and accessing it triggers a page...

5.9AI score0.00114EPSS
SaveExploits0References8Affected Software1
Cvelist
Cvelist
•added 2026/05/06 11:28 a.m.•69 views

CVE-2026-43262 gfs2: fiemap page fault fix

In the Linux kernel, the following vulnerability has been resolved: gfs2: fiemap page fault fix In gfs2fiemap, we are calling iomapfiemap while holding the inode glock. This can lead to recursive glock taking if the fiemap buffer is memory mapped to the same inode and accessing it triggers a page...

0.00114EPSS
SaveExploits0References7
osv_azl
osv_azl
•added 2026/05/06 10:16 a.m.•24 views

AZL-85838 CVE-2026-43118 affecting package kernel 6.6.161.1-1

In the Linux kernel, the following vulnerability has been resolved: btrfs: fix zero size inode with non-zero size after log replay When logging that an inode exists, as part of logging a new name or logging new dir entries for a directory, we always set the generation of the logged inode item to ...

5.5CVSS5.8AI score0.00156EPSS
SaveExploits0References1
NVD
NVD
•added 2026/05/06 10:16 a.m.•25 views

CVE-2026-43118

In the Linux kernel, the following vulnerability has been resolved: btrfs: fix zero size inode with non-zero size after log replay When logging that an inode exists, as part of logging a new name or logging new dir entries for a directory, we always set the generation of the logged inode item to ...

5.5CVSS0.00156EPSS
SaveExploits0References6
NVD
NVD
•added 2026/05/06 10:16 a.m.•23 views

CVE-2026-43076

In the Linux kernel, the following vulnerability has been resolved: ocfs2: validate inline data isize during inode read When reading an inode from disk, ocfs2validateinodeblock performs various sanity checks but does not validate the size of inline data. If the filesystem is corrupted, an inode's...

7.8CVSS0.00131EPSS
SaveExploits0References8
NVD
NVD
•added 2026/05/06 10:16 a.m.•22 views

CVE-2026-43075

In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix out-of-bounds write in ocfs2writeendinline KASAN reports a use-after-free write of 4086 bytes in ocfs2writeendinline, called from ocfs2writeendnolock during a copyfilerange splice fallback on a corrupted ocfs2 filesyst...

7.8CVSS0.00126EPSS
SaveExploits0References8
CVE
CVE
•added 2026/05/06 7:40 a.m.•68 views

CVE-2026-43118

This CVE-2026-43118 concerns a Btrfs log replay data integrity issue in the Linux kernel where truncating a file to zero and then creating a hardlink, followed by a power failure and log replay, could leave the original size unchanged. Root cause: during inode logging, a 0 generation is written f...

5.5CVSS5.8AI score0.00156EPSS
SaveExploits0References6Affected Software1
osv_cve
osv_cve
•added 2026/05/06 7:40 a.m.•22 views

CVE-2026-43118 btrfs: fix zero size inode with non-zero size after log replay

In the Linux kernel, the following vulnerability has been resolved: btrfs: fix zero size inode with non-zero size after log replay When logging that an inode exists, as part of logging a new name or logging new dir entries for a directory, we always set the generation of the logged inode item to ...

6.3AI score
SaveExploits0References9
attackerkb
attackerkb
•added 2026/05/06 7:40 a.m.•20 views

CVE-2026-43118

In the Linux kernel, the following vulnerability has been resolved: btrfs: fix zero size inode with non-zero size after log replay When logging that an inode exists, as part of logging a new name or logging new dir entries for a directory, we always set the generation of the logged inode item to ...

6AI score0.00156EPSS
SaveExploits0References4Affected Software1
Rows per page
Query Builder