CVE-2023-54195
Last modified
CVE-2023-54195 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix timeout of a call that hasn't yet been granted a channel afs_make_call() calls rxrpc_kernel_begin_call() to begin a call (which may get stalled in the background waiting for a connection to become available); it then calls rxrpc_kernel_set_max_life() to set the timeouts - but that starts the call timer so the call timer might then expire before we get a connection assigned - leading to the following oops if the call stalled: BUG: kernel NULL pointer dereference, address: 0000000000000000 ... CPU: 1 PID: 5111 Comm: krxrpcio/0 Not tainted 6.3.0-rc7-build3+ #701 RIP: 0010:rxrpc_alloc_txbuf+0xc0/0x157 ... Call Trace: <TASK> rxrpc_send_ACK+0x50/0x13b rxrpc_input_call_event+0x16a/0x67d rxrpc_io_thread+0x1b6/0x45f ? _raw_spin_unlock_irqrestore+0x1f/0x35 ? rxrpc_input_packet+0x519/0x519 kthread+0xe7/0xef ? kthread_complete_and_exit+0x1b/0x1b ret_from_fork+0x22/0x30 Fix this by noting the timeouts in struct rxrpc_call when the call is created. The timer will be started when the first packet is transmitted. It shouldn't be possible to trigger this directly from userspace through AF_RXRPC as sendmsg() will return EBUSY if the call is in the waiting-for-conn state if it dropped out of the wait due to a signal.. EPSS estimates a 0.17% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix timeout of a call that hasn't yet been granted a channel afs_make_call() calls rxrpc_kernel_begin_call() to begin a call (which may get stalled in the background waiting for a connection to become available); it then calls rxrpc_kernel_set_max_life() to set the timeouts - but that starts the call timer so the call timer might then expire before we get a connection assigned - leading to the following oops if the call stalled: BUG: kernel NULL pointer dereference, address: 0000000000000000 ... CPU: 1 PID: 5111 Comm: krxrpcio/0 Not tainted 6.3.0-rc7-build3+ #701 RIP: 0010:rxrpc_alloc_txbuf+0xc0/0x157 ... Call Trace: <TASK> rxrpc_send_ACK+0x50/0x13b rxrpc_input_call_event+0x16a/0x67d rxrpc_io_thread+0x1b6/0x45f ? _raw_spin_unlock_irqrestore+0x1f/0x35 ? rxrpc_input_packet+0x519/0x519 kthread+0xe7/0xef ? kthread_complete_and_exit+0x1b/0x1b ret_from_fork+0x22/0x30 Fix this by noting the timeouts in struct rxrpc_call when the call is created. The timer will be started when the first packet is transmitted. It shouldn't be possible to trigger this directly from userspace through AF_RXRPC as sendmsg() will return EBUSY if the call is in the waiting-for-conn state if it dropped out of the wait due to a signal.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 9d35d880e0e4a3ab32d8c12f9e4d76198aadd42d, < 92128a7170a220b5126d09a1c1954a3a8d46cef3; >= 9d35d880e0e4a3ab32d8c12f9e4d76198aadd42d, < 72f4a9f3f447948cf86dffe1c4a4c8a429ab9666; >= 9d35d880e0e4a3ab32d8c12f9e4d76198aadd42d, < db099c625b13a74d462521a46d98a8ce5b53af5d |
| Linux | Linux | 6.2 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2023-54195?
How severe is CVE-2023-54195?
How do I fix CVE-2023-54195?
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 2023
- CVE-2023-5419The Funnelforms Free plugin for WordPress is vulnerable to u…4.3
- CVE-2023-54190In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54191In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54192In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54193In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-54194In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54196In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54197In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54198In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-54199In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54200In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-54201In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2023-54195?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
