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-2023-53081ocfs2: fix data corruption after failed write

Description

In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix data corruption after failed write When buffered write fails to copy data into underlying page cache page, ocfs2_write_end_nolock() just zeroes out and dirties the page. This can leave dirty page beyond EOF and if page writeback tries to write this page before write succeeds and expands i_size, page gets into inconsistent state where page dirty bit is clear but buffer dirty bits stay set resulting in page data never getting written and so data copied to the page is lost. Fix the problem by invalidating page beyond EOF after failed write.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 13 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-2023-53081, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.21% · top 88% of all CVEs (20 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 7ed80e77c908cbaa686529a49f8ae0060c5caee7 – < 1629f6f522b2d058019710466a84b240683bbee3
    • affected 7ce2b16bad2cbfa3fa7bbc42c4448914f639ca47 – < c26f3ff4c0be590c1250f945ac2e4fc5fcdc5f45
    • affected f8a6a2ed4b7d1c3c8631eeb6d00572bc853094a8 – < 4c24eb49ab44351424ac8fe8567f91ea48a06089
    • affected 6dbf7bb555981fb5faf7b691e8f6169fc2b2e63b – < 91d7a4bd5656552d6259e2d0f8859f9e8cc5ef68
    • affected 6dbf7bb555981fb5faf7b691e8f6169fc2b2e63b – < a9e53869cb43c96d6d851c491fd4e26430ab6ba6
    • affected 6dbf7bb555981fb5faf7b691e8f6169fc2b2e63b – < 47eb055ad3588fc96d34e9e1dd87b210ce62906b
    • affected 6dbf7bb555981fb5faf7b691e8f6169fc2b2e63b – < 205759c6c18f54659b0b5976b14a52d1b3eb9f57
    • affected 6dbf7bb555981fb5faf7b691e8f6169fc2b2e63b – < 90410bcf873cf05f54a32183afff0161f44f9715
    • affected acef5107e2eacb08a16ad5db60320d65bd26a6c0
    • affected 36ed9e604215f58cec0381ca5fcc6da05f2d87ca
    • affected 4.14.204 – < 4.14.312
    • affected 4.19.155 – < 4.19.280
    • affected 5.4.75 – < 5.4.240
    • affected 4.9.242 – < 4.10
    • affected 5.9.5 – < 5.10
  • Linux · Linux

    • affected 5.10
    • unaffected < 5.10
    • unaffected 4.14.312 – ≤ 4.14.*
    • unaffected 4.19.280 – ≤ 4.19.*
    • unaffected 5.4.240 – ≤ 5.4.*
    • unaffected 5.10.177 – ≤ 5.10.*
    • unaffected 5.15.105 – ≤ 5.15.*
    • unaffected 6.1.21 – ≤ 6.1.*
    • unaffected 6.2.8 – ≤ 6.2.*
    • unaffected 6.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .