Lucene search
+L

9 matches found

SUSE CVE
SUSE CVE
•added 2026/05/07 2:18 a.m.•23 views

SUSE 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.3CVSS5.8AI score0.00156EPSS
SaveExploits0References17
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
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
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
Cvelist
Cvelist
•added 2026/05/06 7:40 a.m.•61 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 ...

0.00156EPSS
SaveExploits0References6
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
Positive Technologies
Positive Technologies
•added 2026/05/06 12:00 a.m.•22 views

PT-2026-37428

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description An issue exists in the Btrfs file system where an inode may retain a non-zero size after log replay, even if it was truncated to zero. This occurs because when logging that an inode exis...

5.5CVSS5.4AI score0.00156EPSS
SaveExploits0References56
Rows per page
Query Builder