Linux Kernel up to 6.3.1 init_resync null pointer dereference

CVSS Meta Temp Score CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.	Current Exploit Price (≈) Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.	CTI Interest Score Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.5	$0-$5k	0.00

Summaryinfo

A vulnerability identified as critical has been detected in Linux Kernel up to 6.3.1. This issue affects the function init_resync. This manipulation causes null pointer dereference. This vulnerability is tracked as CVE-2023-53832. No exploit exists. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.3.1. It has been declared as critical. Affected by this vulnerability is the function init_resync. The manipulation with an unknown input leads to a null pointer dereference vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: md/raid10: fix null-ptr-deref in raid10_sync_request init_resync() inits mempool and sets conf->have_replacemnt at the beginning of sync, close_sync() frees the mempool when sync is completed. After [1] recovery might be skipped and init_resync() is called but close_sync() is not. null-ptr-deref occurs with r10bio->dev[i].repl_bio. The following is one way to reproduce the issue. 1) create a array, wait for resync to complete, mddev->recovery_cp is set to MaxSector. 2) recovery is woken and it is skipped. conf->have_replacement is set to 0 in init_resync(). close_sync() not called. 3) some io errors and rdev A is set to WantReplacement. 4) a new device is added and set to A's replacement. 5) recovery is woken, A have replacement, but conf->have_replacemnt is 0. r10bio->dev[i].repl_bio will not be alloced and null-ptr-deref occurs. Fix it by not calling init_resync() if recovery skipped. [1] commit 7e83ccbecd60 ("md/raid10: Allow skipping recovery when clean arrays are assembled")

It is possible to read the advisory at git.kernel.org. This vulnerability is known as CVE-2023-53832 since 12/09/2025. Technical details of the vulnerability are known, but there is no available exploit.

The vulnerability scanner Nessus provides a plugin with the ID 302405 (EulerOS 2.0 SP10 : kernel (EulerOS-SA-2026-1313)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 4.19.283, 5.4.243, 5.10.180, 5.15.111, 6.1.28, 6.2.15 or 6.3.2 eliminates this vulnerability. Applying the patch 38d33593260536840b49fd1dcac9aedfd14a9d42/14964127be77884003976a392c9faa9ebaabbbe1/bdbf104b1c91fbf38f82c522ebf75429f094292a/68695084077e3de9d3e94e09238ace2b6f246446/b50fd1c3d9d0175aa29ff2706ef36cc178bc356a/99b503e4edc5938885d839cf0e7571963f75d800/9e9efc77efd1956cc244af975240f2513d78a371/a405c6f0229526160aa3f177f65e20c86fce84c5 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 (302405) and CERT Bund (WID-SEC-2025-2765). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Affected

• Debian Linux
• Amazon Linux 2
• Red Hat Enterprise Linux
• Ubuntu Linux
• SUSE Linux
• Oracle Linux
• SUSE openSUSE
• Open Source Linux Kernel
• RESF Rocky Linux

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 4.19.282
• 5.4.242
• 5.10.179
• 5.15.110
• 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.2.0
• 6.2.1
• 6.2.2
• 6.2.3
• 6.2.4
• 6.2.5
• 6.2.6
• 6.2.7
• 6.2.8
• 6.2.9
• 6.2.10
• 6.2.11
• 6.2.12
• 6.2.13
• 6.2.14
• 6.3.0
• 6.3.1

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.7
VulDB Meta Temp Score: 5.5

VulDB Base Score: 5.7
VulDB Temp Score: 5.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

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: 🔍

Exploitinginfo

Class: Null pointer dereference
CWE: CWE-476 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
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: 302405
Nessus Name: EulerOS 2.0 SP10 : kernel (EulerOS-SA-2026-1313)

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 4.19.283/5.4.243/5.10.180/5.15.111/6.1.28/6.2.15/6.3.2
Patch: 38d33593260536840b49fd1dcac9aedfd14a9d42/14964127be77884003976a392c9faa9ebaabbbe1/bdbf104b1c91fbf38f82c522ebf75429f094292a/68695084077e3de9d3e94e09238ace2b6f246446/b50fd1c3d9d0175aa29ff2706ef36cc178bc356a/99b503e4edc5938885d839cf0e7571963f75d800/9e9efc77efd1956cc244af975240f2513d78a371/a405c6f0229526160aa3f177f65e20c86fce84c5

Timelineinfo

12/09/2025 Advisory disclosed
12/09/2025 +0 days CVE reserved
12/09/2025 +0 days VulDB entry created
03/30/2026 +110 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2023-53832 (🔒)
GCVE (CVE): GCVE-0-2023-53832
GCVE (VulDB): GCVE-100-334987
CERT Bund: WID-SEC-2025-2765 - Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Entryinfo

Created: 12/09/2025 09:15
Updated: 03/30/2026 01:53
Changes: 12/09/2025 09:15 (58), 03/16/2026 21:23 (2), 03/30/2026 01:53 (7)
Complete: 🔍
Cache ID: 216:73D:103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

Do you know our Splunk app?

Download it now for free!