CVE-2024-53090: afs: Fix lock recursion
Noroxi assessment
Priority: Monitor (action score 22/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.67% (FIRST EPSS); higher than 52.7% of all records.
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 610a79ffea02102899a1373fe226d949944a7ed6, 9ada9ff6339d49df2260bb876ccf895d88928f81, d256a7f2385cf59d09526c794367d44fd7a26c7a.
- Severity is disputed: the assigning authority (CNA) scores it 7.5, NVD 5.5.
Low priority for now. Upgrade to Linux Linux 610a79ffea02102899a1373fe226d949944a7ed6, 9ada9ff6339d49df2260bb876ccf895d88928f81, d256a7f2385cf59d09526c794367d44fd7a26c7a 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: 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>
- Published
- Nov 21, 2024
- Updated
- Oct 30, 2026
- EPSS
- 0.6% · 52th percentile
- CWE
- CWE-674
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 7.5
- 2.0 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
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
- 4.15affected
- 20acbd9a7aeee0b0af7107f3de791a52c949f3ac and later · before d256a7f2385cf59d09526c794367d44fd7a26c7aaffected · git
- 20acbd9a7aeee0b0af7107f3de791a52c949f3ac and later · before 9ada9ff6339d49df2260bb876ccf895d88928f81affected · git
- 20acbd9a7aeee0b0af7107f3de791a52c949f3ac and later · before d7cbf81df996b1eae2dee8deb6df08e2eba78661affected · git
- 20acbd9a7aeee0b0af7107f3de791a52c949f3ac and later · before 610a79ffea02102899a1373fe226d949944a7ed6affected · git
- before 4.15not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
- 6.11.9 and later · up to and including 6.11.*not affected · semver
- 6.12 and laternot affected · original_commit_for_fix
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 6.11.9
- linux linux kernel6.12
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.192-1 | 6.1.192-1 |
| Debian:13 | linux | before 6.11.9-1 | 6.11.9-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-53092Nov 21, 2024 · virtio_pci: Fix admin vq cleanup by using correct info pointer22Monitor
- ← EarlierCVE-2024-53093Nov 21, 2024 · nvme-multipath: defer partition scanning22Monitor
- Later →CVE-2024-53091Nov 21, 2024 · bpf: Add sk_is_inet and IS_ICSK check in tls_sw_has_ctx_tx/rx22Monitor
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 | 610a79ffea02102899a1373fe226d949944a7ed6 | Vendor (CNA) |
| Linux Linux | 9ada9ff6339d49df2260bb876ccf895d88928f81 | Vendor (CNA) |
| Linux Linux | d256a7f2385cf59d09526c794367d44fd7a26c7a | Vendor (CNA) |
| Linux Linux | d7cbf81df996b1eae2dee8deb6df08e2eba78661 | Vendor (CNA) |
| debian:linux | 6.1.192-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.11.9-1 · Debian:13 | Package registry (OSV) |
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.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-43185531 days apartksmbd: fix signededness bug in smb_direct_prepare_negotiation()39Monitor
- CVE-2024-35886186 days apartipv6: Fix infinite recursion in fib6_dump_done().31Monitor
- CVE-2025-38459246 days apartatm: clip: Fix infinite recursive call of clip_push().31Monitor
- CVE-2024-4499678 days apartvsock: fix recursive ->recvmsg calls22Monitor
- CVE-2023-52986126 days apartbpf, sockmap: Check for any of tcp_bpf_prots when cloning a listener22Monitor
- CVE-2022-49782161 days apartperf: Improve missing SIGTRAP checking22Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-674 · Uncontrolled RecursionCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.