Authenticated file access via skipped single-byte lock checks
Published Sep 17, 2026 · Updated Sep 18, 2026
Improper lock enforcement in affected Linux ksmbd versions allows remote authenticated users to bypass conflicting byte-range locks. The check_lock_range() function treats start == end as empty even though its inclusive range represents one byte, so reads, writes, copychunk requests, and truncation skip conflict checks. An authenticated SMB session must target a locked byte; successful requests can read or modify that byte despite another client's mandatory lock.
Summary
What happened
Improper lock enforcement in affected Linux ksmbd versions allows remote authenticated users to bypass conflicting byte-range locks. The check_lock_range() function treats start == end as empty even though its inclusive range represents one byte, so reads, writes, copychunk requests, and truncation skip conflict checks. An authenticated SMB session must target a locked byte; successful requests can read or modify that byte despite another client's mandatory lock.
The record
- CVE
- CVE-2026-90176
- Published
- Sep 17, 2026
- Updated
- Sep 18, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-362, T1565.001, T1039
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 18, 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=52fcbb92e0d3acfd1448b2a43b6595d540da5295 <a89cc145832e81c32199d4ca2e1ea8bd51ed601d
- Affected versionversion=571204e4758a528fbd67330bd4b0dfbdafb33dd8 <84c2d8e807ac489f5c91769293fb15dfdae8bae8
- Affected versionversion=5d510ac31626ed157d2182149559430350cf2104 <07a9e289ff7edcc004f58952405f8a65c4e37512
- Affected versionversion=5d510ac31626ed157d2182149559430350cf2104 <d40c24634fe077a0dc91fd11fccf44ce12b454d5
- Affected versionversion=6.1.160 <6.1.188
- Affected versionversion=6.12.64 <6.12.110
- Affected versionversion=6.18.3 <6.18.52
- Affected versionversion=6.19
- Affected versionversion=6.6.120 <6.6.157
- Affected versionversion=a6f4cfa3783804336491e0edcb250c25f9b59d33 <f751d6e39d4c937c45f8fedc66699aa7d2d52288
- Affected versionversion=da29cd197246c85c0473259f1cad897d9d28faea <993e0158331d37c04da18efe551b5e1e35fb3078
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.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started