erofs: fix missing xas_retry() in fscache mode
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 |
|
|
In the Linux kernel, the following vulnerability has been resolved:
erofs: fix missing xas_retry() in fscache mode
The xarray iteration only holds the RCU read lock and thus may encounter XA_RETRY_ENTRY if there's process modifying the xarray concurrently. This will cause oops when referring to the invalid entry.
Fix this by adding the missing xas_retry(), which will make the iteration wind back to the root node if XA_RETRY_ENTRY is encountered.
From the CVE record · Linux
EROS fscache mode can encounter an invalid xarray entry when another process modifies the xarray during iteration, causing a kernel oops. The input does not establish whether an attacker can trigger this or what access would be required.
Teams running Linux kernels that use EROFS fscache mode should check their kernel versions; affected versions are not specified.