Local system crash via stale CIFS hostname
Published May 18, 2023 · Updated Mar 18, 2025
Use-after-free in the CIFS client in Linux Kernel before 6.1-rc3 allows local users to crash the system during a failed mount. cifs_put_tcp_session frees server->hostname without nulling it, so the cifsd reconnect thread later dereferences the stale pointer in reconn_set_ipaddr_from_hostname. Reaching the fault requires local access that can initiate a CIFS mount and a failed connection; the grounded consequence is a system crash.
Summary
What happened
Use-after-free in the CIFS client in Linux Kernel before 6.1-rc3 allows local users to crash the system during a failed mount. cifs_put_tcp_session frees server->hostname without nulling it, so the cifsd reconnect thread later dereferences the stale pointer in reconn_set_ipaddr_from_hostname. Reaching the fault requires local access that can initiate a CIFS mount and a failed connection; the grounded consequence is a system crash.
The record
- CVE
- CVE-2023-1195
- Published
- May 18, 2023
- Updated
- Mar 18, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 18, 2023CVE publishedPublication date reported by the CVE source.
- Mar 18, 2025Record 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=prior to kernel 6.1 rc3
What conditions does exploitation require?
What is affected?
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.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo