CVE-2023-53419

rcu: Protect rcu_print_task_exp_stall() ->exp_tasks access

MEDIUM
5.5
CVSS Score
Published: September 18, 2025 at 04:04 PM UTC
Updated: June 17, 2026 at 06:45 AM 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
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: rcu: Protect rcu_print_task_exp_stall() ->exp_tasks access For kernels built with CONFIG_PREEMPT_RCU=y, the following scenario can result in a NULL-pointer dereference: CPU1 CPU2 rcu_preempt_deferred_qs_irqrestore rcu_print_task_exp_stall if (special.b.blocked) READ_ONCE(rnp->exp_tasks) != NULL raw_spin_lock_rcu_node np = rcu_next_node_entry(t, rnp) if (&t->rcu_node_entry == rnp->exp_tasks) WRITE_ONCE(rnp->exp_tasks, np) .... raw_spin_unlock_irqrestore_rcu_node raw_spin_lock_irqsave_rcu_node t = list_entry(rnp->exp_tasks->prev, struct task_struct, rcu_node_entry) (if rnp->exp_tasks is NULL, this will dereference a NULL pointer) The problem is that CPU2 accesses the rcu_node structure's->exp_tasks field without holding the rcu_node structure's ->lock and CPU2 did not observe CPU1's change to rcu_node structure's ->exp_tasks in time. Therefore, if CPU1 sets rcu_node structure's->exp_tasks pointer to NULL, then CPU2 might dereference that NULL pointer. This commit therefore holds the rcu_node structure's ->lock while accessing that structure's->exp_tasks field. [ paulmck: Apply Frederic Weisbecker feedback. ]

Affected

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

v < 5.10.1815.11 ≤ v < 5.15.1135.16 ≤ v < 6.1.305.8 ≤ v < 5.10.1815.8 ≤ v < 5.15.1135.8 ≤ v < 6.1.305.8 ≤ v < 6.3.45.8 ≤ v < 6.46.2 ≤ v < 6.3.4314eeb43e5f22856b281c91c966e51e5782a34985.8
Vendor states this is fixed in 2bc0ae94ef1f9ed322d8ee439de3239ea3632ab2 (fixed)
Vendor states this is fixed in 3c1566bca3f8349f12b75d0a2d5e4a20ad6262ec (fixed)
Vendor states this is fixed in a7d21b8585894e6fff973f6ddae42f02b13f600f (fixed)
Vendor states this is fixed in d0a8c0e31a09ec1efd53079083e2a677956b4d91 (fixed)
Vendor states this is fixed in e30a55e98ae6c44253d8b129efefd5da5bc6e3bc (fixed)
Vendor states this is fixed in 5.10.181 (unaffected)
Vendor states this is fixed in 5.15.113 (unaffected)
Vendor states this is fixed in 5.8 (unaffected)
Vendor states this is fixed in 6.1.30 (unaffected)
Vendor states this is fixed in 6.3.4 (unaffected)
Vendor states this is fixed in 6.4 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.5MEDIUMCISA-ADP
Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-476

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card