In the Linux kernel, the following vulnerability has been resolved:
afs: Fix lock recursion
afs_wake_up_async_call() can incur lock recursion. The problem is that it
is called from AF_RXRPC whilst holding the ->notify_lock, but it tries to
take a ref on the afs_call struct in order to pass it to a work queue - but
if the afs_call is already queued, we then have an extraneous ref that must
be put... calling afs_put_call() may call back down into AF_RXRPC through
rxrpc_kernel_shutdown_call(), however, which might try taking the
->notify_lock again.
This case isn't very common, however, so defer it to a workqueue. The oops
looks something like:
BUG: spinlock recursion on CPU#0, krxrpcio/7001/1646
lock: 0xffff888141399b30, .magic: dead4ead, .owner: krxrpcio/7001/1646, .owner_cpu: 0
CPU: 0 UID: 0 PID: 1646 Comm: krxrpcio/7001 Not tainted 6.12.0-rc2-build3+ #4351
Hardware name: ASUS All Series/H97-PLUS, BIOS 2306 10/09/2014
Call Trace:
<TASK>
dump_stack_lvl+0x47/0x70
do_raw_spin_lock+0x3c/0x90
rxrpc_kernel_shutdown_call+0x83/0xb0
afs_put_call+0xd7/0x180
rxrpc_notify_socket+0xa0/0x190
rxrpc_input_split_jumbo+0x198/0x1d0
rxrpc_input_data+0x14b/0x1e0
? rxrpc_input_call_packet+0xc2/0x1f0
rxrpc_input_call_event+0xad/0x6b0
rxrpc_input_packet_on_conn+0x1e1/0x210
rxrpc_input_packet+0x3f2/0x4d0
rxrpc_io_thread+0x243/0x410
? __pfx_rxrpc_io_thread+0x10/0x10
kthread+0xcf/0xe0
? __pfx_kthread+0x10/0x10
ret_from_fork+0x24/0x40
? __pfx_kthread+0x10/0x10
ret_from_fork_asm+0x1a/0x30
</TASK>
Security readout for executives and security teams
Plain-English summary
CVE-2024-53090 is a Linux kernel availability flaw in AFS/RXRPC handling. Under specific local conditions, a low-privileged user could trigger a kernel spinlock recursion and crash-like failure. The sources show no confidentiality or integrity impact and no KEV-listed exploitation.
Executive priority
Treat as a scheduled but important kernel maintenance item. It is not evidenced as actively exploited, but it can affect availability on shared Linux systems. Prioritize exposed multi-user servers and align remediation with normal kernel patch cycles unless local risk is elevated.
Technical view
The flaw is lock recursion in afs_wake_up_async_call(). It can be called while AF_RXRPC holds notify_lock, then release an extra afs_call reference through afs_put_call(), which may re-enter rxrpc_kernel_shutdown_call() and try to take notify_lock again. The reported failure is a spinlock recursion oops. CWE-674 applies.
Likely exposure
Exposure is most relevant to Linux systems running affected kernel versions where AFS/RXRPC code is present and reachable. The provided data lists Linux kernel versions including 4.15 through 6.12 and 6.11.9 as affected, but does not map distributions or package versions.
Exploitation context
The CVSS vector is local, low complexity, low privileges, no user interaction, with high availability impact only. The bundle does not cite active exploitation, public exploit availability, or remote attack paths. KEV status is false.
Researcher notes
Evidence is limited to the CVE description, CVSS data, affected version metadata, and Linux stable commit references. The source bundle does not provide exploit proofs, distro package mappings, operational workarounds, or evidence of in-the-wild exploitation.
Mitigation direction
Apply Linux kernel or distribution updates containing the referenced stable fixes.
Prioritize multi-user Linux systems where local users can access affected kernel functionality.
Check vendor guidance if immediate patching is not possible.
Reboot into the fixed kernel after updating.
Track distribution advisories for backported fixes and package-specific version mapping.
Validation and detection
Inventory Linux kernel versions across affected systems.
Verify the running kernel includes a vendor fix or referenced stable commit.
Confirm whether AFS/RXRPC kernel support is present, loaded, or operationally required.
Review kernel logs for spinlock recursion or oops entries mentioning afs or rxrpc.
After patching, confirm systems booted into the updated kernel.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-674: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-674 · source CWE mapping
Uncontrolled Recursion
Uncontrolled Recursion represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.