f2fs: fix dereference of stale list iterator after loop body
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 8c242db9b8c01b252290e23827163787f07e01d1 · < ed7efc472c00986dcd6903ab6ed165c7fa167674| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
f2fs: fix dereference of stale list iterator after loop body
The list iterator variable will be a bogus pointer if no break was hit. Dereferencing it (cur->page in this case) could load an out-of-bounds/undefined value making it unsafe to use that in the comparision to determine if the specific element was found.
Since 'cur->page' *can* be out-ouf-bounds it cannot be guaranteed that by chance (or intention of an attacker) it matches the value of 'page' even though the correct element was not found.
This is fixed by using a separate list iterator variable for the loop and only setting the original variable if a suitable element was found. Then determing if the element was found is simply checking if the variable is set.
From the CVE record · Linux
In the Linux kernel’s f2fs component, a stale list iterator can be dereferenced when a loop finds no matching element, potentially reading an out-of-bounds or undefined value. The input does not establish whether an attacker can trigger this or specify network access, authentication, or user-interaction requirements.
Engineers running Linux kernels with f2fs should check their installations; affected versions are not specified.