btrfs: fix invalid inode pointer dereferences during log replay
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 401d098f92ea69d8a75f8b845daf343e511681ba, Kernel 2dcf838cf5c2f0f4501edaa1680fcad03618d760 and Kernel ba8386d662cc51cc5382688bbf7a152b0b0b27cf.
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix invalid inode pointer dereferences during log replay In a few places where we call read_one_inode(), if we get a NULL pointer we end up jumping into an error path, or fallthrough in case of __add_inode_ref(), where we then do something like this: iput(&inode->vfs_inode); which results in an invalid inode pointer that triggers an invalid memory access, resulting in a crash. Fix this by making sure we don't do such dereferences.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.15, >=0502d1127436a69b8c2e7cf309ae0ebff3332668 <401d098f92ea69d8a75f8b845daf343e511681ba, >=b4c50cbb01a1b6901d2b94469636dd80fa93de81 <2dcf838cf5c2f0f4501edaa1680fcad03618d760, >=b4c50cbb01a1b6901d2b94469636dd80fa93de81 <ba8386d662cc51cc5382688bbf7a152b0b0b27cf | 401d098f92ea69d8a75f8b845daf343e511681ba, 2dcf838cf5c2f0f4501edaa1680fcad03618d760, ba8386d662cc51cc5382688bbf7a152b0b0b27cf |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket