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-45864fs/ntfs3: prevent infinite loops caused by the next valid being the same

Description

In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: prevent infinite loops caused by the next valid being the same When processing valid within the range [valid : pos), if valid cannot be retrieved correctly, for example, if the retrieved valid value is always the same, this can trigger a potential infinite loop, similar to the hung problem reported by syzbot [1]. Adding a check for the valid value within the loop body, and terminating the loop and returning -EINVAL if the value is the same as the current value, can prevent this. [1] INFO: task syz.4.21:6056 blocked for more than 143 seconds. Call Trace: rwbase_write_lock+0x14f/0x750 kernel/locking/rwbase_rt.c:244 inode_lock include/linux/fs.h:1027 [inline] ntfs_file_write_iter+0xe6/0x870 fs/ntfs3/file.c:1284

Timeline

  1. ID reserved

    By Linux

  2. · 14 days later

    Published

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-45864, by who scored it
Scored byCVSSScoreVector
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.16% · top 95% 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: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 4342306f0f0d5ff4315a204d315c1b51b914fca5 – < 50c822fcb36768f1fb356f05b02a2248ef81936d
    • affected 4342306f0f0d5ff4315a204d315c1b51b914fca5 – < 6d93239b4fc479f7c0a412dd196ec0ca2672d14a
    • affected 4342306f0f0d5ff4315a204d315c1b51b914fca5 – < 71c8b966ec56e13c02388c1312910588bb49be7a
    • affected 4342306f0f0d5ff4315a204d315c1b51b914fca5 – < b97e371e5d1c13d722335d46eb8bc1a22b272a0e
    • affected 4342306f0f0d5ff4315a204d315c1b51b914fca5 – < 4bf3bafb8e0635ed93e3cd4156dcbcc0fb960cb4
    • affected 4342306f0f0d5ff4315a204d315c1b51b914fca5 – < a47a2bb9aa6455d5cee1045814a60c749309c92b
    • affected 4342306f0f0d5ff4315a204d315c1b51b914fca5 – < 27b75ca4e51e3e4554dc85dbf1a0246c66106fd3
  • Linux · Linux

    • affected 5.15
    • unaffected < 5.15
    • unaffected 5.15.202 – ≤ 5.15.*
    • unaffected 6.1.165 – ≤ 6.1.*
    • unaffected 6.6.128 – ≤ 6.6.*
    • unaffected 6.12.75 – ≤ 6.12.*
    • unaffected 6.18.14 – ≤ 6.18.*
    • unaffected 6.19.4 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .