Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-35821ubifs: Set page uptodate in the correct place

Description

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

  1. ID reserved

    By Linux

  2. Published

  3. · 24 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-35821, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.57% · top 52% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.5.

Affected products

  • Linux · Linux

    • affected 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d – < 4aa554832b9dc9e66249df75b8f447d87853e12e
    • affected 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d – < 778c6ad40256f1c03244fc06d7cdf71f6b5e7310
    • affected 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d – < 8f599ab6fabbca4c741107eade70722a98adfd9f
    • affected 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d – < f19b1023a3758f40791ec166038d6411c8894ae3
    • affected 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d – < 142d87c958d9454c3cffa625fab56f3016e8f9f3
    • affected 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d – < fc99f4e2d2f1ce766c14e98463c2839194ae964f
    • affected 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d – < 4b7c4fc60d6a46350fbe54f5dc937aeaa02e675e
    • affected 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d – < 17772bbe9cfa972ea1ff827319f6e1340de76566
    • affected 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d – < 723012cab779eee8228376754e22c6594229bf8f
  • Linux · Linux

    • affected 2.6.27
    • unaffected < 2.6.27
    • unaffected 4.19.312 – ≤ 4.19.*
    • unaffected 5.4.274 – ≤ 5.4.*
    • unaffected 5.10.215 – ≤ 5.10.*
    • unaffected 5.15.154 – ≤ 5.15.*
    • unaffected 6.1.84 – ≤ 6.1.*
    • unaffected 6.6.24 – ≤ 6.6.*
    • unaffected 6.7.12 – ≤ 6.7.*
    • unaffected 6.8.3 – ≤ 6.8.*
    • unaffected 6.9 – ≤ *

References

References11

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-35821 badge
[![CVE-2024-35821](https://cveledger.app/badge/CVE-2024-35821.svg)](https://cveledger.app/cve/CVE-2024-35821)

Record last updated .