CVE-2023-52623 is a Linux kernel SUNRPC flaw in net/sunrpc/xprtmultipath.c that permits traversal of an RCU-protected list without an RCU read-side lock. The issue was observed during cthon testing against an ONTAP server using pNFS, where it generated an RCU warning. A low-privileged local user can exploit the condition without user interaction, with availability as the rated impact; Red Hat assigns a CVSS v3.1 score of 5.5 and classifies it as CWE-362.
The upstream fix changes rpc_xprt_switch_has_addr() to always acquire rcu_read_lock(), including when invoked by callers that already hold the lock. Corrected stable kernels include 4.19.307, 5.4.269, 5.10.210, 5.15.149, 6.1.77, 6.6.16, 6.7.4, and 6.8. Red Hat has released fixes for affected RHEL 8 kernel and kernel-rt packages and RHEL 9.4 Extended Update Support; RHEL 9 remains affected, while its kernel-rt fix is deferred. Organizations should deploy current vendor-supported kernel updates rather than cherry-picking the upstream patch.

See real exploitation activity before you spend the cycle.
4 events from the most recent confirmed update back to the earliest known activity.
Red Hat released RHSA-2024:5101 for the RHEL 8 kernel and RHSA-2024:5102 for the RHEL 8 real-time kernel, fixing CVE-2023-52623.
Red Hat published its CVE record for the Linux kernel SUNRPC race-condition vulnerability, rating it Low severity with a CVSS v3.1 score of 5.5 and potential availability impact from local exploitation.
Red Hat released RHSA-2025:9584 to fix CVE-2023-52623 in the Red Hat Enterprise Linux 9.4 Extended Update Support kernel.
The Linux kernel CVE team identified CVE-2023-52623 as an unsafe RCU-protected list traversal in net/sunrpc/xprtmultipath.c. The remediation makes rpc_xprt_switch_has_addr() acquire rcu_read_lock() unconditionally, and fixes were made available in stable kernel versions from 4.19.307 through 6.8.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See real exploitation activity behind this advisory so you can triage it against everything else in the queue.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.