- Vulnerability/
- CVE-2024-55641
CVE-2024-55641: xfs: unlock inodes when erroring out of xfs_trans_alloc_dir
First published: Sat Jan 11 2025(Updated: )
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.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | ||
| debian/linux | 5.10.223-1 5.10.234-1 6.1.129-1 6.1.128-1 6.12.21-1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/53b001a21c9dff73b64e8c909c41991f01d5d00f
- https://git.kernel.org/stable/c/6aefe5d97ae57b1343dc60d8bb6a4ed070e5bcea
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-55641
- https://nvd.nist.gov/vuln/detail/CVE-2024-55641
- https://launchpad.net/bugs/cve/CVE-2024-55641
- https://security-tracker.debian.org/tracker/CVE-2024-55641
- https://ubuntu.com/security/CVE-2024-55641
- https://git.kernel.org/linus/53b001a21c9dff73b64e8c909c41991f01d5d00f
Frequently Asked Questions
What is the severity of CVE-2024-55641?
CVE-2024-55641 is considered a moderate risk vulnerability affecting the Linux kernel.
How do I fix CVE-2024-55641?
To fix CVE-2024-55641, update the Linux kernel to the latest version that includes the security patch.
What systems are affected by CVE-2024-55641?
CVE-2024-55641 affects systems running the vulnerable versions of the Linux kernel utilizing the XFS filesystem.
What type of issue is identified in CVE-2024-55641?
CVE-2024-55641 is related to a metadata I/O error occurring in the XFS filesystem during directory allocation.
Is there any workaround for CVE-2024-55641?
There are currently no known workarounds for CVE-2024-55641; upgrading the kernel is the recommended action.
- agent/severity
- agent/title
- agent/first-publish-date
- agent/type
- collector/nvd-api
- source/NVD
- agent/author
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- collector/usn-cve
- source/Ubuntu
- agent/guess-ai
- agent/software-canonical-lookup
- agent/references
- agent/softwarecombine
- collector/launchpad-cve
- source/Launchpad
- agent/source
- agent/description
- agent/event
- collector/nvd-cve
- agent/tags
- collector/security-tracker-debian
- source/Debian
- vendor/linux
- canonical/linux kernel
- package-manager/debian