btrfs: fix iteration of extrefs during log replay
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
btrfs: fix iteration of extrefs during log replay
At __inode_add_ref() when processing extrefs, if we jump into the next label we have an undefined value of victim_name.len, since we haven't initialized it before we did the goto. This results in an invalid memory access in the next iteration of the loop since victim_name.len was not initialized to the length of the name of the current extref.
Fix this by initializing victim_name.len with the current extref's name length.
From the CVE record · Linux
The Linux kernel's btrfs log replay can use an uninitialized name length while processing extended references, causing an invalid memory access. The input does not establish how an attacker could trigger this condition or whether access or user interaction is required.
Operators running Linux kernels with btrfs should check whether their kernel is affected; affected versions were not provided.