btrfs: fix invalid inode pointer dereferences during log replay
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.15.56.16In 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.
From the CVE record · Linux
The Linux kernel’s btrfs log replay can dereference a NULL inode pointer, causing an invalid memory access and a crash. The input does not specify an attack route, authentication requirements, or whether user interaction is needed.
Engineers running Linux kernels with btrfs should check their kernel vendor’s advisory; affected versions were not provided.