| From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2024-55641: xfs: unlock inodes when erroring out of xfs_trans_alloc_dir |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| xfs: unlock inodes when erroring out of xfs_trans_alloc_dir |
| |
| Debugging a filesystem patch with generic/475 caused the system to hang |
| after observing the following sequences in dmesg: |
| |
| XFS (dm-0): metadata I/O error in "xfs_imap_to_bp+0x61/0xe0 [xfs]" at daddr 0x491520 len 32 error 5 |
| XFS (dm-0): metadata I/O error in "xfs_btree_read_buf_block+0xba/0x160 [xfs]" at daddr 0x3445608 len 8 error 5 |
| XFS (dm-0): metadata I/O error in "xfs_imap_to_bp+0x61/0xe0 [xfs]" at daddr 0x138e1c0 len 32 error 5 |
| XFS (dm-0): log I/O error -5 |
| 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. |
| XFS (dm-0): Please unmount the filesystem and rectify the problem(s) |
| XFS (dm-0): Internal error dqp->q_ino.reserved < dqp->q_ino.count at line 869 of file fs/xfs/xfs_trans_dquot.c. Caller xfs_trans_dqresv+0x236/0x440 [xfs] |
| XFS (dm-0): Corruption detected. Unmount and run xfs_repair |
| XFS (dm-0): Unmounting Filesystem be6bcbcc-9921-4deb-8d16-7cc94e335fa7 |
| |
| The system is stuck in unmount trying to lock a couple of inodes so that |
| they can be purged. The dquot corruption notice above is a clue to what |
| happened -- a link() call tried to set up a transaction to link a child |
| into a directory. Quota reservation for the transaction failed after IO |
| errors shut down the filesystem, but then we forgot to unlock the inodes |
| on our way out. Fix that. |
| |
| The Linux kernel CVE team has assigned CVE-2024-55641 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.10 with commit bd5562111d58392298a3c3b93caad71dff681b4b and fixed in 6.12.6 with commit 6aefe5d97ae57b1343dc60d8bb6a4ed070e5bcea |
| Issue introduced in 6.10 with commit bd5562111d58392298a3c3b93caad71dff681b4b and fixed in 6.13 with commit 53b001a21c9dff73b64e8c909c41991f01d5d00f |
| |
| Please see https://www.kernel.org for a full list of currently supported |
| kernel versions by the kernel community. |
| |
| Unaffected versions might change over time as fixes are backported to |
| older supported kernel versions. The official CVE entry at |
| https://cve.org/CVERecord/?id=CVE-2024-55641 |
| will be updated if fixes are backported, please check that for the most |
| up to date information about this issue. |
| |
| |
| Affected files |
| ============== |
| |
| The file(s) affected by this issue are: |
| fs/xfs/xfs_trans.c |
| |
| |
| Mitigation |
| ========== |
| |
| The Linux kernel CVE team recommends that you update to the latest |
| stable kernel version for this, and many other bugfixes. Individual |
| changes are never tested alone, but rather are part of a larger kernel |
| release. Cherry-picking individual commits is not recommended or |
| supported by the Linux kernel community at all. If however, updating to |
| the latest release is impossible, the individual changes to resolve this |
| issue can be found at these commits: |
| https://git.kernel.org/stable/c/6aefe5d97ae57b1343dc60d8bb6a4ed070e5bcea |
| https://git.kernel.org/stable/c/53b001a21c9dff73b64e8c909c41991f01d5d00f |
