CVE-2023-54195: rxrpc: Fix timeout of a call that hasn't yet been granted a channel
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
- Fixed version: Linux Linux 72f4a9f3f447948cf86dffe1c4a4c8a429ab9666, 92128a7170a220b5126d09a1c1954a3a8d46cef3, db099c625b13a74d462521a46d98a8ce5b53af5d.
Low priority for now. Upgrade to Linux Linux 72f4a9f3f447948cf86dffe1c4a4c8a429ab9666, 92128a7170a220b5126d09a1c1954a3a8d46cef3, db099c625b13a74d462521a46d98a8ce5b53af5d or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Dec 30, 2025
- Updated
- Oct 28, 2026
- EPSS
- 0.1% · 9th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.2affected
- 9d35d880e0e4a3ab32d8c12f9e4d76198aadd42d and later · before 92128a7170a220b5126d09a1c1954a3a8d46cef3affected · git
- 9d35d880e0e4a3ab32d8c12f9e4d76198aadd42d and later · before 72f4a9f3f447948cf86dffe1c4a4c8a429ab9666affected · git
- 9d35d880e0e4a3ab32d8c12f9e4d76198aadd42d and later · before db099c625b13a74d462521a46d98a8ce5b53af5daffected · git
- before 6.2not affected · semver
- 6.2.16 and later · up to and including 6.2.*not affected · semver
- 6.3.3 and later · up to and including 6.3.*not affected · semver
- 6.4 and laternot affected · original_commit_for_fix
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2023-54193Dec 30, 2025 · net/sched: cls_api: remove block_cb from driver_list before freeing31Monitor
- ← EarlierCVE-2023-54194Dec 30, 2025 · exfat: use kvmalloc_array/kvfree instead of kmalloc_array/kfree0Monitor
- Later →CVE-2023-54196Dec 30, 2025 · fs/ntfs3: Fix NULL pointer dereference in 'ni_write_inode'0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 72f4a9f3f447948cf86dffe1c4a4c8a429ab9666 | Vendor (CNA) |
| Linux Linux | 92128a7170a220b5126d09a1c1954a3a8d46cef3 | Vendor (CNA) |
| Linux Linux | db099c625b13a74d462521a46d98a8ce5b53af5d | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.