CVE-2026-89641
Last modified
CVE-2026-89641 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: cifs: clear tcon after cifsFileInfo_put() in cifs_file_set_size() When the else branch of cifs_file_set_size() finds a writable file handle via find_writable_file(), it borrows tcon and server from the handle's tlink, attempts the handle-based set_file_size() RPC, and then releases the handle with cifsFileInfo_put(). If set_file_size() fails, execution falls through to the path-based fallback, which reuses the borrowed tcon and server under the "if (tcon == NULL)" guard. Since tcon is not NULL at that point, the guard is skipped. EPSS estimates a 0.19% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: cifs: clear tcon after cifsFileInfo_put() in cifs_file_set_size() When the else branch of cifs_file_set_size() finds a writable file handle via find_writable_file(), it borrows tcon and server from the handle's tlink, attempts the handle-based set_file_size() RPC, and then releases the handle with cifsFileInfo_put(). If set_file_size() fails, execution falls through to the path-based fallback, which reuses the borrowed tcon and server under the "if (tcon == NULL)" guard. Since tcon is not NULL at that point, the guard is skipped. If cifsFileInfo_put() dropped the last reference on a tlink that was already removed from the tlink tree (TCON_LINK_IN_TREE cleared, as happens during reconnection or session teardown), cifs_put_tlink() will have freed tcon; the subsequent set_path_size() call is then a use-after-free. Setting tcon = NULL after cifsFileInfo_put() causes the existing guard to take the cifs_sb_tlink() path, which acquires a fresh reference for the path-based operation or fails cleanly if the session is gone.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 110fee6b9bb58a5c50047fc2594d415f741b591e, < 4f18c9e7ee464aaae5cd9fccdb943b3fcb4655d4; >= 110fee6b9bb58a5c50047fc2594d415f741b591e, < 4bea15d9c7683218f57b8c1f5f0aa75cab76af8d; >= 110fee6b9bb58a5c50047fc2594d415f741b591e, < b96db32fed8dfb2478d7c208f89bf383beed1535 |
| Linux | Linux | 6.18 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-89641?
How severe is CVE-2026-89641?
How do I fix CVE-2026-89641?
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-89636In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-89637In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-89638In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-89639In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-8964Spoofing issue in the Popup Blocker component. This vulnerab…7.5
- CVE-2026-89640In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-89642In the Linux kernel, the following vulnerability has been re…
- CVE-2026-89643In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-89644In the Linux kernel, the following vulnerability has been re…
- CVE-2026-89645In the Linux kernel, the following vulnerability has been re…
- CVE-2026-89646In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-89647In the Linux kernel, the following vulnerability has been re…7.5
Are you affected by CVE-2026-89641?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
