CVE-2026-43127·Kernel vulnerability
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.
- Severity
- medium
- Software
- Kernel
- Fixed in
- 6.19.6
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.13% — higher than 2% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Affected versions
From: 6.19
Until: 6.19.6
Fixed in: 6.19.6
How to fix this CVE
Update your Linux kernel to version 6.19.6 or later to resolve a deadlock condition in the NTFS3 filesystem driver. This fix prevents a circular locking dependency that could cause the kernel to hang during MFT (Master File Table) operations on NTFS volumes. Apply the update through your distribution's package manager and reboot your system to complete the remediation.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Check kernel version: uname -r — ensure you are running 6.19.6 or later (or a patched stable branch)
- Verify NTFS3 module is loaded: lsmod | grep ntfs3 — confirms if the vulnerable code path is active
- Monitor dmesg for deadlock warnings: dmesg | grep -i 'circular\|deadlock\|lockdep' — look for locking dependency warnings
- Confirm patch applied: grep -r 'run_unpack_ex\|down_read_trylock' /boot/config-$(uname -r) — verify trylock implementation is present in kernel config or build logs
FAQ
What is CVE-2026-43127?
This vulnerability is a circular locking deadlock in the Linux kernel's NTFS3 filesystem implementation. When the MFT extension and run unpacking routines contend for two locks in opposite orders, the kernel can hang indefinitely during certain filesystem operations on NTFS volumes.
Is CVE-2026-43127 being actively exploited?
No, this CVE is not listed on CISA's Known Exploited Vulnerabilities (KEV) catalog and no public exploits are available. However, it can be triggered accidentally through normal NTFS filesystem activity, making it a reliability rather than a security issue.
What versions of Kernel are affected by CVE-2026-43127?
Linux kernel versions 6.19 through 6.19.5 are affected. The fix is included in kernel 6.19.6 and later stable releases.
How do I check if my server is vulnerable to CVE-2026-43127?
Run 'uname -r' to display your kernel version. If it shows 6.19.0 through 6.19.5, your system is vulnerable. Cross-reference against your distro's kernel package version to confirm.
Does Defensia detect CVE-2026-43127?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the Linux kernel package is installed on a monitored server, CVE-2026-43127 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/08ce2fee1b869ecbfbd94e0eb2630e52203a2e03
- https://git.kernel.org/stable/c/76016d15bbd90caa0ce7765fddf9bde8e943e601
- https://git.kernel.org/stable/c/b014372b62237521444ee51384549bdf48b79015
- https://git.kernel.org/stable/c/b8d22d9d8260b0f4f4d8e2898c98037c9982ea66
- https://git.kernel.org/stable/c/d60f09d2d16c44a797d8cb67015cde2508720506
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-43127. Free for 1 server.
Get started free