In the Linux kernel, the following vulnerability has been resolved: xfs: fix cursor and pointer handling when recovering iunlink buckets LOLLM pointed out a bug in xlog_recover_iunlink_bucket: 1. We don't null out prev_ip after releasing it, which can lead to UAF problems if the inodegc flush call in the loop fails. at which point I noticed even more bugs: 2. If the inodegc flush inside the loop fails, we also leak @ip. 3. We set prev_agino to agino having already advanced agino, which results in inodes with i_prev_unlinked set to itself. 4. If we exit the bottom of the loop with prev_ip set, then prev_ip aliases ip and we also set its i_prev_unlinked to itself. Bugs 3 and 4 introduce loops into the unlinked list, though these loops don't surface because we immediately flush each unlinked inode after loading it. Fix all of these issues.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 8
- StatusReceived → PublishedNVD modified 2026-10-24 14:08
- StatusPublished → ReceivedNVD modified 2026-10-24 14:16
- CVSS7.8 (v3.1, CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H)NVD modified 2026-10-24 14:16
- StatusReceived → PublishedNVD modified 2026-10-21 12:55
- References+1 references (now 5)NVD modified 2026-10-21 13:21
- StatusPublished → ReceivedNVD modified 2026-10-21 13:21
- StatusReceived → PublishedNVD modified 2026-10-19 09:19
- First seenunscoredNVD modified 2026-10-19 10:18
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 5
- https://git.kernel.org/stable/c/47a948ba653a463d429e02fda2f06a3d6b78666d
- https://git.kernel.org/stable/c/65f39d09d73718611cee40399179323b5d4ead00
- https://git.kernel.org/stable/c/66a2179d02668f8df44b1a249899006f3ba38ea0
- https://git.kernel.org/stable/c/8c9d5b8a96d6b93eb24e07b4163c89341ba29bd1
- https://git.kernel.org/stable/c/961c717e6bf0e53c2c2b1fe4aef1add9390fedab