CVE-2024-53174

SUNRPC: make sure cache entry active before cache_show

HIGH

7.8

CVSS Score

Published: December 27, 2024 at 01:49 PM UTC

Updated: August 5, 2026 at 12:05 PM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

HIGH7.8

Exploit prediction

EPSS 0.3%

SSVC

No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: SUNRPC: make sure cache entry active before cache_show The function `c_show` was called with protection from RCU. This only ensures that `cp` will not be freed. Therefore, the reference count for `cp` can drop to zero, which will trigger a refcount use-after-free warning when `cache_get` is called. To resolve this issue, use `cache_get_rcu` to ensure that `cp` remains active. ------------[ cut here ]------------ refcount_t: addition on 0; use-after-free. WARNING: CPU: 7 PID: 822 at lib/refcount.c:25 refcount_warn_saturate+0xb1/0x120 CPU: 7 UID: 0 PID: 822 Comm: cat Not tainted 6.12.0-rc3+ #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.1-2.fc37 04/01/2014 RIP: 0010:refcount_warn_saturate+0xb1/0x120 Call Trace: <TASK> c_show+0x2fc/0x380 [sunrpc] seq_read_iter+0x589/0x770 seq_read+0x1e5/0x270 proc_reg_read+0xe1/0x140 vfs_read+0x125/0x530 ksys_read+0xc1/0x160 do_syscall_64+0x5f/0x170 entry_SYSCALL_64_after_hwframe+0x76/0x7e

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

v < 5.4.2874.20 ≤ v < 5.10.2314.20 ≤ v < 5.15.1744.20 ≤ v < 5.4.2874.20 ≤ v < 6.1.1204.20 ≤ v < 6.11.114.20 ≤ v < 6.12.24.20 ≤ v < 6.134.20 ≤ v < 6.6.645.11 ≤ v < 5.15.1745.16 ≤ v < 6.1.1205.5 ≤ v < 5.10.2316.12 ≤ v < 6.12.26.2 ≤ v < 6.6.646.7 ≤ v < 6.11.114.20d48cf356a13073853f19be6ca5ebbecfc2762ebe

Vendor states this is fixed in 02999e135b013d85c6df738746e8e24699befee4 (fixed)

Vendor states this is fixed in 068c0b50f3f700b94f78850834cd91ae3b34c2c1 (fixed)

Vendor states this is fixed in 2862eee078a4d2d1f584e7f24fa50dddfa5f3471 (fixed)

Vendor states this is fixed in acfaf37888e0f0732fb6a50ff093dce6d99994d0 (fixed)

Vendor states this is fixed in c7dac3af57e38b2054f990e573256d90bf887958 (fixed)

Vendor states this is fixed in d882e2b7fad3f5e5fac66184a347f408813f654a (fixed)

Vendor states this is fixed in e9be26735d055c42543a4d047a769cc6d0fb1504 (fixed)

Vendor states this is fixed in ec305f303bf070b4f6896b7a76009f702956d402 (fixed)

Vendor states this is fixed in 4.20 (unaffected)

Vendor states this is fixed in 5.10.231 (unaffected)

Vendor states this is fixed in 5.15.174 (unaffected)

Vendor states this is fixed in 5.4.287 (unaffected)

Vendor states this is fixed in 6.1.120 (unaffected)

Vendor states this is fixed in 6.11.11 (unaffected)

Vendor states this is fixed in 6.12.2 (unaffected)

Vendor states this is fixed in 6.13 (unaffected)

Vendor states this is fixed in 6.6.64 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references