ubifs: Set page uptodate in the correct place
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d · < fc99f4e2d2f1ce766c14e98463c2839194ae964f| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ubifs: Set page uptodate in the correct place
Page cache reads are lockless, so setting the freshly allocated page uptodate before we've overwritten it with the data it's supposed to have in it will allow a simultaneous reader to see old data. Move the call to SetPageUptodate into ubifs_write_end(), which is after we copied the new data into the page.
From the CVE record · Linux
In the Linux kernel's UBIFS code, a newly allocated page can be marked up to date before new data is copied into it. A simultaneous lockless page-cache reader can then see old data. The input does not specify whether authentication or user interaction is required.
Engineers running Linux kernels that use UBIFS should check their versions; affected versions are not specified.