xfs: fix undersized l_iclog_roundoff values

Description

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.

Timeline

Scores

EPSS (exploitation in 30 days)

0.51% · top 56% of all CVEs (11 Nov 2026)

CISA SSVC

Exploitation: none · Automatable: yes · Technical impact: partial

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.2.

Affected products

• Linux · Linux

  • affected a6a65fef5ef8d0a6a0ce514eb66b2f3dfa777b48 – < 5afae524f83d6a18517298491a5624cb0eae5029
  • affected a6a65fef5ef8d0a6a0ce514eb66b2f3dfa777b48 – < 2ecda4b83749c1fef0c9dea4fd5e8b513aba3e40
  • affected a6a65fef5ef8d0a6a0ce514eb66b2f3dfa777b48 – < 41e91dff2d3974730b5ee50daa8e27ec254cbf91
  • affected a6a65fef5ef8d0a6a0ce514eb66b2f3dfa777b48 – < e88ce9f0536f3b2149afb70625cfc4bd74a4ac6d
  • affected a6a65fef5ef8d0a6a0ce514eb66b2f3dfa777b48 – < 446a1f5bb64ba38adb93cb043ff0f7b85e8937ca
  • affected a6a65fef5ef8d0a6a0ce514eb66b2f3dfa777b48 – < 5e7148402dfc4a5b7894d8e97b15e5c2e70924aa
  • affected a6a65fef5ef8d0a6a0ce514eb66b2f3dfa777b48 – < 52a8a1ba883defbfe3200baa22cf4cd21985d51a

• Linux · Linux

  • affected 5.14
  • unaffected < 5.14
  • unaffected 5.15.203 – ≤ 5.15.*
  • unaffected 6.1.167 – ≤ 6.1.*
  • unaffected 6.6.130 – ≤ 6.6.*
  • unaffected 6.12.78 – ≤ 6.12.*
  • unaffected 6.18.19 – ≤ 6.18.*
  • unaffected 6.19.9 – ≤ 6.19.*
  • unaffected 7.0 – ≤ *

Sources

The same CVE in the primary databases and aggregators, to check against.

• CVE.org record (opens in a new tab)
• CVE List JSON (GitHub) (opens in a new tab)
• NVD (opens in a new tab)
• FIRST EPSS (opens in a new tab)
• EUVD EUVD-2026-28671 (opens in a new tab)
• OSV.dev (opens in a new tab)
• GitHub Advisories (opens in a new tab)
• CIRCL Vulnerability-Lookup (opens in a new tab)

Badge for a README or a ticket

[![CVE-2026-43365](https://cveledger.app/badge/CVE-2026-43365.svg)](https://cveledger.app/cve/CVE-2026-43365)

Record last updated 19 Oct 2026, 19:16 UTC.