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-43127ntfs3: fix circular locking dependency in run_unpack_ex

Description

In the Linux kernel, the following vulnerability has been resolved: ntfs3: fix circular locking dependency in run_unpack_ex Syzbot reported a circular locking dependency between wnd->rw_lock (sbi->used.bitmap) and ni->file.run_lock. The deadlock scenario: 1. ntfs_extend_mft() takes ni->file.run_lock then wnd->rw_lock. 2. run_unpack_ex() takes wnd->rw_lock then tries to acquire ni->file.run_lock inside ntfs_refresh_zone(). This creates an AB-BA deadlock. Fix this by using down_read_trylock() instead of down_read() when acquiring run_lock in run_unpack_ex(). If the lock is contended, skip ntfs_refresh_zone() - the MFT zone will be refreshed on the next MFT operation. This breaks the circular dependency since we never block waiting for run_lock while holding wnd->rw_lock.

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 6 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-43127, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.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.12% · top 98% 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: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 57f7979aefdcef66326bda47e07ee0d8be64bf21 – < d60f09d2d16c44a797d8cb67015cde2508720506
    • affected db7fc56646cafe39599a4c21f1398e2bdfd5c185 – < 76016d15bbd90caa0ce7765fddf9bde8e943e601
    • affected 5fc982fe7eca9d0cf7b25832450ebd4f7c8e1c36 – < b014372b62237521444ee51384549bdf48b79015
    • affected 5fc982fe7eca9d0cf7b25832450ebd4f7c8e1c36 – < b8d22d9d8260b0f4f4d8e2898c98037c9982ea66
    • affected 5fc982fe7eca9d0cf7b25832450ebd4f7c8e1c36 – < 08ce2fee1b869ecbfbd94e0eb2630e52203a2e03
    • affected 6.6.66 – < 6.6.160
    • affected 6.12.5 – < 6.12.114
  • Linux · Linux

    • affected 6.13
    • unaffected < 6.13
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.16 – ≤ 6.18.*
    • unaffected 6.19.6 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .