xfs: resample the data fork mapping after cycling ILOCK
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.15.212, 6.1.178, 6.6.145, 6.12.96, 6.18.39, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: xfs: resample the data fork mapping after cycling ILOCK xfs_reflink_fill_{cow_hole,delalloc} are both presented with an inode, a data fork mapping, and a cow fork mapping. Unfortunately, these two helpers cycle the ILOCK to grab a transaction, which means that the mappings are stale as soon as we reacquire the ILOCK. Currently we refresh the cow fork mapping by re-calling xfs_find_trim_cow_extent, but we don't refresh the data fork mapping beforehand, which means that the xfs_bmap_trim_cow in that function queries the refcount btree about the wrong physical blocks and returns an inaccurate value in *shared. If *shared is now false, the directio write proceeds with a stale data fork mapping. Fix this by querying the data fork mapping if the sequence counter changes across the ILOCK cycle.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5 · fixed in dc11be133efca5fe3a2fb02b016dee825cc12f18; From 3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5 · fixed in b8c9aa832b52680ee40d6cab0efb081f9a69df05; From 3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5 · fixed in 50f0012da1040f69a4e788cd9aed587c9a04983f; From 3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5 · fixed in e705d81a7193dd19e69b8e2bad4696d78a4ea075; From 3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5 · fixed in 206c09b04dc5469c7ff14d8aceff2d47c88078d9; From 3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5 · fixed in 44f891bc088958399eec27f7604928694aa35581; From 3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5 · fixed in 2f4acd0fcd862e22eab45690ec2c08c80b6ef2e7
- Linux Linux
4.11
- KernelLinux
From 4.11.0 · fixed in 5.15.212; From 5.16.0 · fixed in 6.1.178; From 6.2.0 · fixed in 6.6.145; From 6.7.0 · fixed in 6.12.96; From 6.13.0 · fixed in 6.18.39; From 6.19.0 · fixed in 7.1.4
References 8
git.kernel.org
- stable/c/dc11be133efca5fe3a2fb02b016dee825cc12f18
- stable/c/b8c9aa832b52680ee40d6cab0efb081f9a69df05
- stable/c/50f0012da1040f69a4e788cd9aed587c9a04983f
- stable/c/e705d81a7193dd19e69b8e2bad4696d78a4ea075
- stable/c/206c09b04dc5469c7ff14d8aceff2d47c88078d9
- stable/c/44f891bc088958399eec27f7604928694aa35581
- stable/c/2f4acd0fcd862e22eab45690ec2c08c80b6ef2e7