Local system crash via TIPC connection race
Published Apr 19, 2023 · Updated Mar 19, 2025
NULL pointer dereference in the Linux kernel before 6.1-rc7 allows local users to crash the system through the TIPC protocol. In net/tipc/topsrv.c, tipc_conn_close can observe a newly allocated connection before con->sock is assigned, then dereference con->sock->sk. Reaching the fault requires low-privileged local access, a loaded TIPC module, and winning the data race; the bounded consequence is a system crash.
Summary
What happened
NULL pointer dereference in the Linux kernel before 6.1-rc7 allows local users to crash the system through the TIPC protocol. In net/tipc/topsrv.c, tipc_conn_close can observe a newly allocated connection before con->sock is assigned, then dereference con->sock->sk. Reaching the fault requires low-privileged local access, a loaded TIPC module, and winning the data race; the bounded consequence is a system crash.
The record
- CVE
- CVE-2023-1382
- Published
- Apr 19, 2023
- Updated
- Mar 19, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 19, 2023CVE publishedPublication date reported by the CVE source.
- Mar 19, 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=Linux Kernel prior to Kernel 6.1 RC7
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