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.
CVSS Details
- CVSS 3.1 Base Score: 5.5
- CVSS 3.1 Vector: (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)
Covered by Rapid7
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Debian | — | Upgrade linux | Jul 27, 2026 | Jul 27, 2026 |
| Redhat_linux | — | No solution exists | Jul 9, 2025 | Jan 11, 2025 |
| Ubuntu | — | Upgrade linux-image-oem-24.04aUpgrade linux-image-lowlatencyUpgrade linux-image-generic-64kUpgrade linux-image-generic-64k-hwe-24.04Upgrade linux-image-6.11.0-1011-awsUpgrade linux-image-azure-fdeUpgrade linux-image-lowlatency-hwe-24.04Upgrade linux-image-lowlatency-64k-hwe-24.04Upgrade linux-image-6.11.0-1013-oracleUpgrade linux-image-virtual-hwe-24.04Upgrade linux-image-6.11.0-1012-azure-fdeUpgrade linux-image-6.11.0-1012-azureUpgrade linux-image-virtualUpgrade linux-image-oem-24.04bUpgrade linux-image-lowlatency-64kUpgrade linux-image-6.11.0-21-genericUpgrade linux-image-6.11.0-1007-realtimeUpgrade linux-image-6.11.0-1011-lowlatency-64kUpgrade linux-image-oracleUpgrade linux-image-gcpUpgrade linux-image-genericUpgrade linux-image-oracle-64kUpgrade linux-image-awsUpgrade linux-image-6.11.0-21-generic-64kUpgrade linux-image-6.11.0-1011-gcpUpgrade linux-image-realtime-hwe-24.04Upgrade linux-image-gcp-64kUpgrade linux-image-oem-24.04Upgrade linux-image-6.11.0-1010-raspiUpgrade linux-image-6.11.0-1011-gcp-64kUpgrade linux-image-generic-hwe-24.04Upgrade linux-image-6.11.0-1013-oracle-64kUpgrade linux-image-raspiUpgrade linux-image-6.11.0-1011-lowlatencyUpgrade linux-image-realtimeUpgrade linux-image-6.11.0-1017-oemUpgrade linux-image-azure | Mar 28, 2025 | Jan 11, 2025 |
Prioritise with Active Threat Intelligence
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub