CVE-2026-31717
Last modified
CVE-2026-31717 is a high-severity vulnerability rated 8.8/10 on the CVSS scale. 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. EPSS estimates a 0.44% chance of exploitation in the next 30 days.
Description
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).
Metrics
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.6.32, < 6.7 | — |
| Linux | Linux Kernel | >= 6.9, < 6.18.25 | — |
| Linux | Linux Kernel | >= 6.19, < 7.0.2 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2026-31717?
How severe is CVE-2026-31717?
How do I fix CVE-2026-31717?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-31711In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-31712In the Linux kernel, the following vulnerability has been re…8.3
- CVE-2026-31713In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31714In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31715In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-31716In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-31718In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-31719In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-3172Buffer overflow in parallel HNSW index build in pgvector 0.6…8.1
- CVE-2026-31720In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-31721In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31722In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-31717?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
