Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2024-53090 — kernel

🟠 CVSS 7.5 — High ✅ No Known Exploit NVD
7.5
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

afs: Fix lock recursion

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>

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

  • Attack vector: Network — reachable from anywhere that can route to the service.
  • Attack complexity: Low — the attack works reliably, with no preparation.
  • Privileges required: None — an unauthenticated stranger can try it.
  • User interaction: None — nobody has to be tricked into anything.
  • Scope: Unchanged — the damage stays inside the vulnerable component.
  • Confidentiality impact: None.
  • Integrity impact: None.
  • Availability impact: High — total loss, or loss the attacker controls.

Affected software

CVE-2024-53090 is recorded against 2 packages.

  • kernel (from 4.15.0 up to 6.11.9)
  • linux-kernel

Timeline and source

Published on 21 November 2024 and last revised on 12 August 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

git.kernel.org (Web)
git.kernel.org (Web)
github.com (Advisory)
nvd.nist.gov (Advisory)
git.kernel.org (Package)

Other advisories for this package

kernel has other advisories on record. If you are patching this one, these are worth checking on the same host:

Details

Severity High
CVSS Score 7.5
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CWE N/A
Public Exploit ✅ No
Source NVD
Published 2024-11-21
Updated 2026-08-20
Modified 2026-08-12

Affected Packages

Software From version Fixed in
kernel 4.15.0 6.11.9
linux-kernel — —

Similar Threats

Site Security Check

Is kernel part of your stack?

CVE-2024-53090 is rated CVSS 7.5 High. BotEraser scans your installation against known CVE records and tells you whether this vulnerability applies to the versions you actually run.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2024
✓