btrfs: abort in rename_exchange if we fail to insert the second ref
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 0df50d47d17401f9f140dfbe752a65e5d72f9932, Kernel dc09ef3562726cd520c8338c1640872a60187af5 and Kernel ff8de2cec65a8c8521faade12a31b39c80e49f5b.
In the Linux kernel, the following vulnerability has been resolved: btrfs: abort in rename_exchange if we fail to insert the second ref Error injection stress uncovered a problem where we'd leave a dangling inode ref if we failed during a rename_exchange. This happens because we insert the inode ref for one side of the rename, and then for the other side. If this second inode ref insert fails we'll leave the first one dangling and leave a corrupt file system behind. Fix this by aborting if we did the insert for the first inode ref.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =4.7, >=cdd1fedf8261cd7a73c0596298902ff4f0f04492 <0df50d47d17401f9f140dfbe752a65e5d72f9932, >=cdd1fedf8261cd7a73c0596298902ff4f0f04492 <dc09ef3562726cd520c8338c1640872a60187af5, >=cdd1fedf8261cd7a73c0596298902ff4f0f04492 <ff8de2cec65a8c8521faade12a31b39c80e49f5b | 0df50d47d17401f9f140dfbe752a65e5d72f9932, dc09ef3562726cd520c8338c1640872a60187af5, ff8de2cec65a8c8521faade12a31b39c80e49f5b |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket