Lock-validation disruption via uninitialized NTFS MFT lock
Published Nov 9, 2024 · Updated May 11, 2026
Improper lock handling in Linux kernel 5.15 through 6.12-rc2 allows local users to disrupt lock validation by closing the NTFS master file table. The ntfs_file_release function acquires ni->file.run_lock for the MFT even though that lock is not explicitly initialized for the MFT inode. The path requires an NTFS volume mounted with preallocation and a last-writer close of the MFT; published evidence shows warnings and disabled lock validation, not a demonstrated privilege gain or system crash.
Summary
What happened
Improper lock handling in Linux kernel 5.15 through 6.12-rc2 allows local users to disrupt lock validation by closing the NTFS master file table. The ntfs_file_release function acquires ni->file.run_lock for the MFT even though that lock is not explicitly initialized for the MFT inode. The path requires an NTFS volume mounted with preallocation and a last-writer close of the MFT; published evidence shows warnings and disabled lock validation, not a demonstrated privilege gain or system crash.
The record
- CVE
- CVE-2024-50242
- Published
- Nov 9, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 9, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4534a70b7056fd4b9a1c6db5a4ce3c98546b291e <031d6f608290c847ba6378322d0986d08d1a645a
- Affected versionversion=4534a70b7056fd4b9a1c6db5a4ce3c98546b291e <542532afe249588ae88d8409d4bf861c315f8862
- Affected versionversion=4534a70b7056fd4b9a1c6db5a4ce3c98546b291e <550ef40fa6366d5d11b122e5f36b1f9aa20c087e
- Affected versionversion=4534a70b7056fd4b9a1c6db5a4ce3c98546b291e <82685eb6ca1db2bd11190451085bcb86ed03aa24
- Affected versionversion=4534a70b7056fd4b9a1c6db5a4ce3c98546b291e <d1ac7e2620302e3e49573df39bd4e868e8b4962a
- Affected versionversion=5.15
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
- syzbot ntfs_file_release reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo