CVE-2024-35821
ubifs: Set page uptodate in the correct place
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
2.6.27
References 9
git.kernel.org
- stable/c/4aa554832b9dc9e66249df75b8f447d87853e12e
- stable/c/778c6ad40256f1c03244fc06d7cdf71f6b5e7310
- stable/c/8f599ab6fabbca4c741107eade70722a98adfd9f
- stable/c/f19b1023a3758f40791ec166038d6411c8894ae3
- stable/c/142d87c958d9454c3cffa625fab56f3016e8f9f3
- stable/c/fc99f4e2d2f1ce766c14e98463c2839194ae964f
- stable/c/4b7c4fc60d6a46350fbe54f5dc937aeaa02e675e
- stable/c/17772bbe9cfa972ea1ff827319f6e1340de76566
- stable/c/723012cab779eee8228376754e22c6594229bf8f