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-89835f2fs: avoid NULL checkpoint thread access in sysfs

Description

In the Linux kernel, the following vulnerability has been resolved: f2fs: avoid NULL checkpoint thread access in sysfs checkpoint_merge can be enabled even when no checkpoint merge thread is running. A read-only mount is one case: f2fs does not start f2fs_issue_ckpt there, but ckpt_thread_ioprio is still writable through sysfs. The ckpt_thread_ioprio store path updates the saved ioprio value and, when checkpoint_merge is enabled, calls set_task_ioprio() for the checkpoint thread. If cprc->f2fs_issue_ckpt is NULL, that dereferences a NULL task pointer. Protect ckpt_thread_ioprio sysfs writes with s_umount as well, so the checkpoint thread cannot disappear under the store path while updating its ioprio.

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 44 days 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 88% of all CVEs (13 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected e65920661708b7c0f3db45c9cd5d0095034ee37f – < 54196bcfde998fb37009f50e0ef16498f651f0f9
    • affected e65920661708b7c0f3db45c9cd5d0095034ee37f – < 22760e3e9cecbddc475edc91600787abf407a302
    • affected e65920661708b7c0f3db45c9cd5d0095034ee37f – < a6573f3ffc19542de9ebc1a2b1f930fd48ba538c
    • affected e65920661708b7c0f3db45c9cd5d0095034ee37f – < aefcec3bebdeed2bff444378122300763325ba23
    • affected e65920661708b7c0f3db45c9cd5d0095034ee37f – < 8f3b99c50dd0da1777994ce7c7e60d39b9f60f4b
    • affected e65920661708b7c0f3db45c9cd5d0095034ee37f – < 5cb33b00c8fbb6e8f1fa3d281c3036d5f7c7c41f
  • Linux · Linux

    • affected 5.12
    • unaffected < 5.12
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.51 – ≤ 6.18.*
    • unaffected 7.2.5 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .