Description
In the Linux kernel, the following vulnerability has been resolved: xfs: bound inode fork length against the fork size during log recovery xlog_recover_inode_commit_pass2() copies an inode log item's data/attr fork region into the inode buffer using the on-log region length without bounding it against the fork capacity, e.g.: len = item->ri_buf[2].iov_len; memcpy(XFS_DFORK_DPTR(dip), src, len); The only guard is an ASSERT, which is a no-op on production kernels (CONFIG_XFS_DEBUG off), and xfs_dinode_verify() runs only after the copy. A crafted image with a dirty log can therefore drive a heap out-of-bounds write at mount time. The XFS_ILOG_DBROOT sibling already passes XFS_DFORK_DSIZE as a bound; the DDATA/DEXT and ADATA/AEXT memcpy paths did not. Bound each logged fork region against the destination fork size before copying it, and reject the log item with -EFSCORRUPTED when it does not fit. Because the recovered inode is only verified after the fork data has been copied in, the checks are done up front, before any memcpy into the on-disk inode.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
658fa68b6f34f73c7e4023489accd34c1db91cb1 to < af559d87fdd921b90c86125f78d8b97d754432ddaffected658fa68b6f34f73c7e4023489accd34c1db91cb1 to < f2cc5001ffcc1d8e5e16607ce4b6920ea30c2cfeaffected658fa68b6f34f73c7e4023489accd34c1db91cb1 to < e2768e65a5f2f942c831e3df3b06ad7332d423e6affected658fa68b6f34f73c7e4023489accd34c1db91cb1 to < 9232301894a06e664d8de2da97175cf98419bd16affected
Linux Linux
Default version status: affected
5.8affected0 to < 5.8unaffected6.12.117 to ≤ 6.12.*unaffected6.18.61 to ≤ 6.18.*unaffected7.3.2 to ≤ 7.3.*unaffected7.4-rc1 to ≤ *unaffected