CVE-2026-90176: ksmbd: Do not skip lock checks for single-byte ranges
Noroxi assessment
Priority: Monitor (action score 32/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.50% (FIRST EPSS).
- Anyone who can reach it over the internet 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 07a9e289ff7edcc004f58952405f8a65c4e37512, 6.1.188, 6.12.110.
Low priority for now. Upgrade to Linux Linux 07a9e289ff7edcc004f58952405f8a65c4e37512, 6.1.188, 6.12.110 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: ksmbd: Do not skip lock checks for single-byte ranges check_lock_range() uses inclusive ranges. Its callers pass the end offset as start + length - 1, so start == end represents a valid single-byte range rather than an empty range. The start == end shortcut therefore skips mandatory byte-range lock checks for one-byte reads, writes, copychunk operations and one-byte truncate ranges. A conflicting lock covering that byte is not checked and the operation is allowed to proceed. Remove the shortcut. The truncate size == inode->i_size case is already handled by only calling check_lock_range() when the new size differs from the current file size.
- Published
- Sep 17, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.5% · 42th percentile
- CWE
- —
Report tools
Action score
32
Monitor
Low priority for now.
- CVSS
- 32 / 40 · 8.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.1
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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.
—
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
- 6.19affected
- 52fcbb92e0d3acfd1448b2a43b6595d540da5295 and later · before a89cc145832e81c32199d4ca2e1ea8bd51ed601daffected · git
- da29cd197246c85c0473259f1cad897d9d28faea and later · before 993e0158331d37c04da18efe551b5e1e35fb3078affected · git
- a6f4cfa3783804336491e0edcb250c25f9b59d33 and later · before f751d6e39d4c937c45f8fedc66699aa7d2d52288affected · git
- 571204e4758a528fbd67330bd4b0dfbdafb33dd8 and later · before 84c2d8e807ac489f5c91769293fb15dfdae8bae8affected · git
- 5d510ac31626ed157d2182149559430350cf2104 and later · before 07a9e289ff7edcc004f58952405f8a65c4e37512affected · git
- 5d510ac31626ed157d2182149559430350cf2104 and later · before d40c24634fe077a0dc91fd11fccf44ce12b454d5affected · git
- 6.1.160 and later · before 6.1.188affected · semver
- 6.6.120 and later · before 6.6.157affected · semver
- 6.12.64 and later · before 6.12.110affected · semver
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.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-90174Sep 17, 2026 · ksmbd: fix slab-out-of-bounds read in ksmbd_alloc_user()28Monitor
- ← EarlierCVE-2026-90175Sep 17, 2026 · smb: server: fix leak of ksmbd_ipc_login_request_ext() returned buffer0Monitor
- Later →CVE-2026-90177Sep 17, 2026 · bpf: Check pointer type for all atomic RMW paths31Monitor
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 | 07a9e289ff7edcc004f58952405f8a65c4e37512 | Vendor (CNA) |
| Linux Linux | 6.1.188 | Vendor (CNA) |
| Linux Linux | 6.12.110 | Vendor (CNA) |
| Linux Linux | 6.18.52 | Vendor (CNA) |
| Linux Linux | 6.6.157 | Vendor (CNA) |
| Linux Linux | 84c2d8e807ac489f5c91769293fb15dfdae8bae8 | Vendor (CNA) |
| Linux Linux | 993e0158331d37c04da18efe551b5e1e35fb3078 | Vendor (CNA) |
| Linux Linux | a89cc145832e81c32199d4ca2e1ea8bd51ed601d | Vendor (CNA) |
| Linux Linux | d40c24634fe077a0dc91fd11fccf44ce12b454d5 | Vendor (CNA) |
| Linux Linux | f751d6e39d4c937c45f8fedc66699aa7d2d52288 | Vendor (CNA) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet 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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
nvd-secondary
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/84c2d8e807ac489f5c91769293fb15dfdae8bae8
- git.kernel.org/stable/c/993e0158331d37c04da18efe551b5e1e35fb3078
- git.kernel.org/stable/c/a89cc145832e81c32199d4ca2e1ea8bd51ed601d
- git.kernel.org/stable/c/d40c24634fe077a0dc91fd11fccf44ce12b454d5
- git.kernel.org/stable/c/f751d6e39d4c937c45f8fedc66699aa7d2d52288
Vendor advisories and official records. Exploit/PoC links are deliberately left out.