Answer in brief
CVE-2026-43127 records a Unknown severity vulnerability in ntfs3: fix circular locking dependency in run_unpack_ex. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=57f7979aefdcef66326bda47e07ee0d8be64bf21 <d60f09d2d16c44a797d8cb67015cde2508720506 || >=db7fc56646cafe39599a4c21f1398e2bdfd5c185 <76016d15bbd90caa0ce7765fddf9bde8e943e601 || >=5fc982fe7eca9d0cf7b25832450ebd4f7c8e1c36 <b014372b62237521444ee51384549bdf48b79015 || >=5fc982fe7eca9d0cf7b25832450ebd4f7c8e1c36 <b8d22d9d8260b0f4f4d8e2898c98037c9982ea66 || >=5fc982fe7eca9d0cf7b25832450ebd4f7c8e1c36 <08ce2fee1b869ecbfbd94e0eb2630e52203a2e03 || >=6.6.66 <6.6.160 || >=6.12.5 <6.12.114 | d60f09d2d16c44a797d8cb67015cde2508720506, 76016d15bbd90caa0ce7765fddf9bde8e943e601, b014372b62237521444ee51384549bdf48b79015, b8d22d9d8260b0f4f4d8e2898c98037c9982ea66, 08ce2fee1b869ecbfbd94e0eb2630e52203a2e03, 6.6.160, 6.12.114 |
| Linux/Linuxgeneric | 6.13 | Not reported |
Published upstream
May 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 21, 2026
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.
Quoted source text, attributed separately from HOL analysis.