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-2026-23234f2fs: fix to avoid UAF in f2fs_write_end_io()

Description

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid UAF in f2fs_write_end_io() As syzbot reported an use-after-free issue in f2fs_write_end_io(). It is caused by below race condition: loop device umount - worker_thread - loop_process_work - do_req_filebacked - lo_rw_aio - lo_rw_aio_complete - blk_mq_end_request - blk_update_request - f2fs_write_end_io - dec_page_count - folio_end_writeback - kill_f2fs_super - kill_block_super - f2fs_put_super : free(sbi) : get_pages(, F2FS_WB_CP_DATA) accessed sbi which is freed In kill_f2fs_super(), we will drop all page caches of f2fs inodes before call free(sbi), it guarantee that all folios should end its writeback, so it should be safe to access sbi before last folio_end_writeback(). Let's relocate ckpt thread wakeup flow before folio_end_writeback() to resolve this issue.

Timeline

  1. ID reserved

    By Linux

  2. · 50 days later

    Published

  3. · 2 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-2026-23234, 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.14% · top 97% of all CVEs (18 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 e234088758fca3a669ebb1a02d8bf7bf60f0e4ff – < 0fb58aff0dafd6837cc91f4154f3ed6e020358fa
    • affected e234088758fca3a669ebb1a02d8bf7bf60f0e4ff – < 2f67ff1e15a8a4d0e4ffc6564ab20d03d7398fe9
    • affected e234088758fca3a669ebb1a02d8bf7bf60f0e4ff – < 505e1c0530db6152cab3feef8e3e4da3d3e358c9
    • affected e234088758fca3a669ebb1a02d8bf7bf60f0e4ff – < acc2c97fc0005846e5cf11b5ba3189fef130c9b3
    • affected e234088758fca3a669ebb1a02d8bf7bf60f0e4ff – < cf4a9e1bc8129eb63fda5f8bdcd8d87f0bd76f42
    • affected e234088758fca3a669ebb1a02d8bf7bf60f0e4ff – < 995030be4ce6338c6ff814583c14166446a64008
    • affected e234088758fca3a669ebb1a02d8bf7bf60f0e4ff – < a42f99be8a16b32a0bb91bb6dda212a6ad61be5d
    • affected e234088758fca3a669ebb1a02d8bf7bf60f0e4ff – < ce2739e482bce8d2c014d76c4531c877f382aa54
  • Linux · Linux

    • affected 3.13
    • unaffected < 3.13
    • unaffected 5.10.251 – ≤ 5.10.*
    • unaffected 5.15.201 – ≤ 5.15.*
    • unaffected 6.1.164 – ≤ 6.1.*
    • unaffected 6.6.127 – ≤ 6.6.*
    • unaffected 6.12.74 – ≤ 6.12.*
    • unaffected 6.18.13 – ≤ 6.18.*
    • unaffected 6.19.3 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .