Answer in brief
CVE-2026-43365 records a Unknown severity vulnerability in xfs: fix undersized l_iclog_roundoff values. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=a6a65fef5ef8d0a6a0ce514eb66b2f3dfa777b48 <5afae524f83d6a18517298491a5624cb0eae5029 || >=a6a65fef5ef8d0a6a0ce514eb66b2f3dfa777b48 <2ecda4b83749c1fef0c9dea4fd5e8b513aba3e40 || >=a6a65fef5ef8d0a6a0ce514eb66b2f3dfa777b48 <41e91dff2d3974730b5ee50daa8e27ec254cbf91 || >=a6a65fef5ef8d0a6a0ce514eb66b2f3dfa777b48 <e88ce9f0536f3b2149afb70625cfc4bd74a4ac6d || >=a6a65fef5ef8d0a6a0ce514eb66b2f3dfa777b48 <446a1f5bb64ba38adb93cb043ff0f7b85e8937ca || >=a6a65fef5ef8d0a6a0ce514eb66b2f3dfa777b48 <5e7148402dfc4a5b7894d8e97b15e5c2e70924aa || >=a6a65fef5ef8d0a6a0ce514eb66b2f3dfa777b48 <52a8a1ba883defbfe3200baa22cf4cd21985d51a | 5afae524f83d6a18517298491a5624cb0eae5029, 2ecda4b83749c1fef0c9dea4fd5e8b513aba3e40, 41e91dff2d3974730b5ee50daa8e27ec254cbf91, e88ce9f0536f3b2149afb70625cfc4bd74a4ac6d, 446a1f5bb64ba38adb93cb043ff0f7b85e8937ca, 5e7148402dfc4a5b7894d8e97b15e5c2e70924aa, 52a8a1ba883defbfe3200baa22cf4cd21985d51a |
| Linux/Linuxgeneric | 5.14 | Not reported |
Published upstream
May 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: xfs: fix undersized l_iclog_roundoff values If the superblock doesn't list a log stripe unit, we set the incore log roundoff value to 512. This leads to corrupt logs and unmountable filesystems in generic/617 on a disk with 4k physical sectors... XFS (sda1): Mounting V5 Filesystem ff3121ca-26e6-4b77-b742-aaff9a449e1c XFS (sda1): Torn write (CRC failure) detected at log block 0x318e. Truncating head block from 0x3197. XFS (sda1): failed to locate log tail XFS (sda1): log mount/recovery failed: error -74 XFS (sda1): log mount failed XFS (sda1): Mounting V5 Filesystem ff3121ca-26e6-4b77-b742-aaff9a449e1c XFS (sda1): Ending clean mount ...on the current xfsprogs for-next which has a broken mkfs. xfs_info shows this... meta-data=/dev/sda1 isize=512 agcount=4, agsize=644992 blks = sectsz=4096 attr=2, projid32bit=1 = crc=1 finobt=1, sparse=1, rmapbt=1 = reflink=1 bigtime=1 inobtcount=1 nrext64=1 = exchange=1 metadir=1 data = bsize=4096 blocks=2579968, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0, ftype=1, parent=1 log =internal log bsize=4096 blocks=16384, version=2 = sectsz=4096 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 = rgcount=0 rgsize=268435456 extents = zoned=0 start=0 reserved=0 ...observe that the log section has sectsz=4096 sunit=0, which means that the roundoff factor is 512, not 4096 as you'd expect. We should fix mkfs not to generate broken filesystems, but anyone can fuzz the ondisk superblock so we should be more cautious. I think the inadequate logic predates commit a6a65fef5ef8d0, but that's clearly going to require a different backport.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-43365 records a Unknown severity vulnerability in xfs: fix undersized l_iclog_roundoff values. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=a6a65fef5ef8d0a6a0ce514eb66b2f3dfa777b48 <5afae524f83d6a18517298491a5624cb0eae5029 || >=a6a65fef5ef8d0a6a0ce514eb66b2f3dfa777b48 <2ecda4b83749c1fef0c9dea4fd5e8b513aba3e40 || >=a6a65fef5ef8d0a6a0ce514eb66b2f3dfa777b48 <41e91dff2d3974730b5ee50daa8e27ec254cbf91 || >=a6a65fef5ef8d0a6a0ce514eb66b2f3dfa777b48 <e88ce9f0536f3b2149afb70625cfc4bd74a4ac6d || >=a6a65fef5ef8d0a6a0ce514eb66b2f3dfa777b48 <446a1f5bb64ba38adb93cb043ff0f7b85e8937ca || >=a6a65fef5ef8d0a6a0ce514eb66b2f3dfa777b48 <5e7148402dfc4a5b7894d8e97b15e5c2e70924aa || >=a6a65fef5ef8d0a6a0ce514eb66b2f3dfa777b48 <52a8a1ba883defbfe3200baa22cf4cd21985d51a | 5afae524f83d6a18517298491a5624cb0eae5029, 2ecda4b83749c1fef0c9dea4fd5e8b513aba3e40, 41e91dff2d3974730b5ee50daa8e27ec254cbf91, e88ce9f0536f3b2149afb70625cfc4bd74a4ac6d, 446a1f5bb64ba38adb93cb043ff0f7b85e8937ca, 5e7148402dfc4a5b7894d8e97b15e5c2e70924aa, 52a8a1ba883defbfe3200baa22cf4cd21985d51a |
| Linux/Linuxgeneric | 5.14 | Not reported |
Published upstream
May 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: xfs: fix undersized l_iclog_roundoff values If the superblock doesn't list a log stripe unit, we set the incore log roundoff value to 512. This leads to corrupt logs and unmountable filesystems in generic/617 on a disk with 4k physical sectors... XFS (sda1): Mounting V5 Filesystem ff3121ca-26e6-4b77-b742-aaff9a449e1c XFS (sda1): Torn write (CRC failure) detected at log block 0x318e. Truncating head block from 0x3197. XFS (sda1): failed to locate log tail XFS (sda1): log mount/recovery failed: error -74 XFS (sda1): log mount failed XFS (sda1): Mounting V5 Filesystem ff3121ca-26e6-4b77-b742-aaff9a449e1c XFS (sda1): Ending clean mount ...on the current xfsprogs for-next which has a broken mkfs. xfs_info shows this... meta-data=/dev/sda1 isize=512 agcount=4, agsize=644992 blks = sectsz=4096 attr=2, projid32bit=1 = crc=1 finobt=1, sparse=1, rmapbt=1 = reflink=1 bigtime=1 inobtcount=1 nrext64=1 = exchange=1 metadir=1 data = bsize=4096 blocks=2579968, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0, ftype=1, parent=1 log =internal log bsize=4096 blocks=16384, version=2 = sectsz=4096 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 = rgcount=0 rgsize=268435456 extents = zoned=0 start=0 reserved=0 ...observe that the log section has sectsz=4096 sunit=0, which means that the roundoff factor is 512, not 4096 as you'd expect. We should fix mkfs not to generate broken filesystems, but anyone can fuzz the ondisk superblock so we should be more cautious. I think the inadequate logic predates commit a6a65fef5ef8d0, but that's clearly going to require a different backport.
Quoted source text, attributed separately from HOL analysis.