CVE-2023-53163: fs/ntfs3: don't hold ni_lock when calling truncate_setsize()
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0226635c304cfd5c9db9b78c259cb713819b057e, 6bb6b1c6b0c31e36736b87a39dd1cbbd9d5ec22f, 73fee7e1e5ea11b51c51c46e0577a197ca3602cf.
Low priority for now. Upgrade to Linux Linux 0226635c304cfd5c9db9b78c259cb713819b057e, 6bb6b1c6b0c31e36736b87a39dd1cbbd9d5ec22f, 73fee7e1e5ea11b51c51c46e0577a197ca3602cf or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: don't hold ni_lock when calling truncate_setsize() syzbot is reporting hung task at do_user_addr_fault() [1], for there is a silent deadlock between PG_locked bit and ni_lock lock. Since filemap_update_page() calls filemap_read_folio() after calling folio_trylock() which will set PG_locked bit, ntfs_truncate() must not call truncate_setsize() which will wait for PG_locked bit to be cleared when holding ni_lock lock.
- Published
- Sep 15, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- —
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.15affected
- 4342306f0f0d5ff4315a204d315c1b51b914fca5 and later · before 8414983c2e649364d8af29080a0869266b31abb6affected · git
- 4342306f0f0d5ff4315a204d315c1b51b914fca5 and later · before 6bb6b1c6b0c31e36736b87a39dd1cbbd9d5ec22faffected · git
- 4342306f0f0d5ff4315a204d315c1b51b914fca5 and later · before 73fee7e1e5ea11b51c51c46e0577a197ca3602cfaffected · git
- 4342306f0f0d5ff4315a204d315c1b51b914fca5 and later · before 0226635c304cfd5c9db9b78c259cb713819b057eaffected · git
- before 5.15not affected · semver
- 5.15.87 and later · up to and including 5.15.*not affected · semver
- 6.0.19 and later · up to and including 6.0.*not affected · semver
- 6.1.5 and later · up to and including 6.1.*not affected · semver
- 6.2 and laternot affected · original_commit_for_fix
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.15 and later · before 5.15.87
- linux linux kernel5.16 and later · before 6.0.19
- linux linux kernel6.1 and later · before 6.1.5
- linux linux kernel6.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.7-1 | 6.1.7-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2023-53151Sep 15, 2025 · md/raid10: prevent soft lockup while flush writes22Monitor
- ← EarlierCVE-2023-53152Sep 15, 2025 · drm/amdgpu: fix calltrace warning in amddrm_buddy_fini22Monitor
- Later →CVE-2023-53164Sep 15, 2025 · irqchip/ti-sci: Fix refcount leak in ti_sci_intr_irq_domain_probe22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0226635c304cfd5c9db9b78c259cb713819b057e | Vendor (CNA) |
| Linux Linux | 6bb6b1c6b0c31e36736b87a39dd1cbbd9d5ec22f | Vendor (CNA) |
| Linux Linux | 73fee7e1e5ea11b51c51c46e0577a197ca3602cf | Vendor (CNA) |
| Linux Linux | 8414983c2e649364d8af29080a0869266b31abb6 | Vendor (CNA) |
| debian:linux | 6.1.7-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.