Linux Kernel up to 5.10.180/5.15.112/6.1.29/6.3.3 rcu rcu_print_task_exp_stall null pointer dereference

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in Linux Kernel up to 5.10.180/5.15.112/6.1.29/6.3.3. This issue affects the function rcu_print_task_exp_stall of the component rcu. The manipulation results in null pointer dereference.
This vulnerability is known as CVE-2023-53419. No exploit is available.
You should upgrade the affected component.
Details
A vulnerability classified as critical has been found in Linux Kernel up to 5.10.180/5.15.112/6.1.29/6.3.3. Affected is the function rcu_print_task_exp_stall of the component rcu. The manipulation with an unknown input leads to a null pointer dereference vulnerability. CWE is classifying the issue as CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. This is going to have an impact on availability. CVE summarizes:
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. ]
The advisory is shared for download at git.kernel.org. This vulnerability is traded as CVE-2023-53419 since 09/17/2025. There are known technical details, but no exploit is available.
The vulnerability scanner Nessus provides a plugin with the ID 265515 (Linux Distros Unpatched Vulnerability : CVE-2023-53419), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 5.10.181, 5.15.113, 6.1.30 or 6.3.4 eliminates this vulnerability. Applying the patch a7d21b8585894e6fff973f6ddae42f02b13f600f/e30a55e98ae6c44253d8b129efefd5da5bc6e3bc/d0a8c0e31a09ec1efd53079083e2a677956b4d91/2bc0ae94ef1f9ed322d8ee439de3239ea3632ab2/3c1566bca3f8349f12b75d0a2d5e4a20ad6262ec is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the databases at Tenable (265515) and CERT Bund (WID-SEC-2025-2092). Once again VulDB remains the best source for vulnerability data.
Affected
- Amazon Linux 2
- Red Hat Enterprise Linux
- SUSE Linux
- Oracle Linux
- SUSE openSUSE
- RESF Rocky Linux
- Open Source Linux Kernel
- Dell Secure Connect Gateway
- IBM QRadar SIEM
Product
Type
Vendor
Name
Version
- 5.10.180
- 5.15.112
- 6.1.0
- 6.1.1
- 6.1.2
- 6.1.3
- 6.1.4
- 6.1.5
- 6.1.6
- 6.1.7
- 6.1.8
- 6.1.9
- 6.1.10
- 6.1.11
- 6.1.12
- 6.1.13
- 6.1.14
- 6.1.15
- 6.1.16
- 6.1.17
- 6.1.18
- 6.1.19
- 6.1.20
- 6.1.21
- 6.1.22
- 6.1.23
- 6.1.24
- 6.1.25
- 6.1.26
- 6.1.27
- 6.1.28
- 6.1.29
- 6.3.0
- 6.3.1
- 6.3.2
- 6.3.3
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.6VulDB Meta Temp Score: 5.5
VulDB Base Score: 5.7
VulDB Temp Score: 5.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Null pointer dereferenceCWE: CWE-476 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 265515
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2023-53419
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 5.10.181/5.15.113/6.1.30/6.3.4
Patch: a7d21b8585894e6fff973f6ddae42f02b13f600f/e30a55e98ae6c44253d8b129efefd5da5bc6e3bc/d0a8c0e31a09ec1efd53079083e2a677956b4d91/2bc0ae94ef1f9ed322d8ee439de3239ea3632ab2/3c1566bca3f8349f12b75d0a2d5e4a20ad6262ec
Timeline
09/17/2025 CVE reserved09/18/2025 Advisory disclosed
09/18/2025 VulDB entry created
12/11/2025 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2023-53419 (🔒)
GCVE (CVE): GCVE-0-2023-53419
GCVE (VulDB): GCVE-100-324900
CERT Bund: WID-SEC-2025-2092 - Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service
Entry
Created: 09/18/2025 19:16Updated: 12/11/2025 19:05
Changes: 09/18/2025 19:16 (59), 09/20/2025 19:24 (7), 09/22/2025 05:43 (2), 11/29/2025 18:26 (1), 12/11/2025 19:05 (10)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.