CVE-2024-55641

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> xfs: unlock inodes when erroring out of xfs_trans_alloc_dir<br /> <br /> Debugging a filesystem patch with generic/475 caused the system to hang<br /> after observing the following sequences in dmesg:<br /> <br /> XFS (dm-0): metadata I/O error in "xfs_imap_to_bp+0x61/0xe0 [xfs]" at daddr 0x491520 len 32 error 5<br /> XFS (dm-0): metadata I/O error in "xfs_btree_read_buf_block+0xba/0x160 [xfs]" at daddr 0x3445608 len 8 error 5<br /> XFS (dm-0): metadata I/O error in "xfs_imap_to_bp+0x61/0xe0 [xfs]" at daddr 0x138e1c0 len 32 error 5<br /> XFS (dm-0): log I/O error -5<br /> XFS (dm-0): Metadata I/O Error (0x1) detected at xfs_trans_read_buf_map+0x1ea/0x4b0 [xfs] (fs/xfs/xfs_trans_buf.c:311). Shutting down filesystem.<br /> XFS (dm-0): Please unmount the filesystem and rectify the problem(s)<br /> XFS (dm-0): Internal error dqp-&gt;q_ino.reserved q_ino.count at line 869 of file fs/xfs/xfs_trans_dquot.c. Caller xfs_trans_dqresv+0x236/0x440 [xfs]<br /> XFS (dm-0): Corruption detected. Unmount and run xfs_repair<br /> XFS (dm-0): Unmounting Filesystem be6bcbcc-9921-4deb-8d16-7cc94e335fa7<br /> <br /> The system is stuck in unmount trying to lock a couple of inodes so that<br /> they can be purged. The dquot corruption notice above is a clue to what<br /> happened -- a link() call tried to set up a transaction to link a child<br /> into a directory. Quota reservation for the transaction failed after IO<br /> errors shut down the filesystem, but then we forgot to unlock the inodes<br /> on our way out. Fix that.