CVE-2026-31717: ksmbd: validate owner of durable handle on reconnect
Noroxi assessment
Priority: Monitor (action score 35/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.43% (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 00ce8d6789dae72d042a4522264964c72891ca37, 49110a8ce654bbe56bef7c5e44cce31f4b102b8a, 6.6.142.
Low priority for now. Upgrade to Linux Linux 00ce8d6789dae72d042a4522264964c72891ca37, 49110a8ce654bbe56bef7c5e44cce31f4b102b8a, 6.6.142 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: validate owner of durable handle on reconnect Currently, ksmbd does not verify if the user attempting to reconnect to a durable handle is the same user who originally opened the file. This allows any authenticated user to hijack an orphaned durable handle by predicting or brute-forcing the persistent ID. According to MS-SMB2, the server MUST verify that the SecurityContext of the reconnect request matches the SecurityContext associated with the existing open. Add a durable_owner structure to ksmbd_file to store the original opener's UID, GID, and account name. and catpure the owner information when a file handle becomes orphaned. and implementing ksmbd_vfs_compare_durable_owner() to validate the identity of the requester during SMB2_CREATE (DHnC).
- Published
- May 1, 2026
- Updated
- Nov 11, 2026
- EPSS
- 0.4% · 38th percentile
- CWE
- —
Report tools
Action score
35
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.8
- 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
- Proof of concept exists, no weaponized module
- 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
- 6.9affected
- 8df4bcdb0a4232192b2445256c39b787d58ef14d and later · before 712cdf917e77a6444ce3836874829d770db20ee6affected · git
- c8efcc786146a951091588e5fa7e3c754850cb3c and later · before c7f0f0d01c88bdcb8b1694d7d321670013f7ed7daffected · git
- c8efcc786146a951091588e5fa7e3c754850cb3c and later · before 00ce8d6789dae72d042a4522264964c72891ca37affected · git
- c8efcc786146a951091588e5fa7e3c754850cb3c and later · before c908c853f304a4969b5aa10eba0b50350cc65b80affected · git
- c8efcc786146a951091588e5fa7e3c754850cb3c and later · before 49110a8ce654bbe56bef7c5e44cce31f4b102b8aaffected · git
- 6.6.32 and later · before 6.6.142affected · semver
- before 6.9not affected · semver
- 6.6.142 and later · up to and including 6.6.*not affected · semver
- 6.12.92 and later · up to and including 6.12.*not affected · semver
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 kernel6.6.32 and later · before 6.7
- linux linux kernel6.9 and later · before 6.18.25
- linux linux kernel6.19 and later · before 7.0.2
- linux linux kernel7.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.12.94-1 | 6.12.94-1 |
| Debian:14 | linux | before 7.0.3-1 | 7.0.3-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-2026-31715May 1, 2026 · f2fs: fix UAF caused by decrementing sbi->nr_pages[] in f2fs_write_end_io()31Monitor
- ← EarlierCVE-2026-31716May 1, 2026 · fs/ntfs3: validate rec->used in journal-replay file record check31Monitor
- Later →CVE-2026-31718May 1, 2026 · ksmbd: fix use-after-free in __ksmbd_close_fd() via durable scavenger39Monitor
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 | 00ce8d6789dae72d042a4522264964c72891ca37 | Vendor (CNA) |
| Linux Linux | 49110a8ce654bbe56bef7c5e44cce31f4b102b8a | Vendor (CNA) |
| Linux Linux | 6.6.142 | Vendor (CNA) |
| Linux Linux | 712cdf917e77a6444ce3836874829d770db20ee6 | Vendor (CNA) |
| Linux Linux | c7f0f0d01c88bdcb8b1694d7d321670013f7ed7d | Vendor (CNA) |
| Linux Linux | c908c853f304a4969b5aa10eba0b50350cc65b80 | Vendor (CNA) |
| debian:linux | 6.12.94-1 · Debian:13 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:5 | 2026-05-04 |
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.
- Published
- First PoC+2 d
- TodayNov 13, 2026+196 d
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
- 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
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.