Linux Kernel up to 6.3.1 raid10_sync_request information disclosure

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.
4.4$0-$5k0.00

Summaryinfo

A vulnerability identified as critical has been detected in Linux Kernel up to 6.3.1. Affected is the function raid10_sync_request. The manipulation leads to information disclosure. This vulnerability is traded as CVE-2023-53299. There is no exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in Linux Kernel up to 6.3.1. This issue affects the function raid10_sync_request. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: md/raid10: fix leak of 'r10bio->remaining' for recovery raid10_sync_request() will add 'r10bio->remaining' for both rdev and replacement rdev. However, if the read io fails, recovery_request_write() returns without issuing the write io, in this case, end_sync_request() is only called once and 'remaining' is leaked, cause an io hang. Fix the problem by decreasing 'remaining' according to if 'bio' and 'repl_bio' is valid.

The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2023-53299 since 09/16/2025. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

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

Upgrading to version 4.14.315, 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 cb827ed2bb34480dc102146d3a1f89fdbcafc028/1d2c6c6e37fe5de11fd01a82badf03390e12df7a/8c5d5d7ffd1e76734811b8ea5417cf0432b9952c/1697fb124c6d6c5237e9cbd78890310154738084/8d09065802c53cc938d162b62f6c4150b392c90e/11141630f03efffdfe260b3582b2d93d38171b97/3481dec5ecbbbbe44ab23e22c2b14bd65c644ec6/4f82e7e07cdaf2947d71968e3d6b73370a217093/26208a7cffd0c7cbf14237ccd20c7270b3ffeb7e 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 (284758) and CERT Bund (WID-SEC-2025-2053). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

  • Debian Linux
  • Amazon Linux 2
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • IBM QRadar SIEM
  • SUSE openSUSE
  • Open Source Linux Kernel
  • RESF Rocky Linux
  • Dell Secure Connect Gateway
  • F5 F5OS

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.5
VulDB Meta Temp Score: 4.4

VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Information disclosure
CWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 284758
Nessus Name: EulerOS 2.0 SP10 : kernel (EulerOS-SA-2026-1029)

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 4.14.315/4.19.283/5.4.243/5.10.180/5.15.111/6.1.28/6.2.15/6.3.2
Patch: cb827ed2bb34480dc102146d3a1f89fdbcafc028/1d2c6c6e37fe5de11fd01a82badf03390e12df7a/8c5d5d7ffd1e76734811b8ea5417cf0432b9952c/1697fb124c6d6c5237e9cbd78890310154738084/8d09065802c53cc938d162b62f6c4150b392c90e/11141630f03efffdfe260b3582b2d93d38171b97/3481dec5ecbbbbe44ab23e22c2b14bd65c644ec6/4f82e7e07cdaf2947d71968e3d6b73370a217093/26208a7cffd0c7cbf14237ccd20c7270b3ffeb7e

Timelineinfo

09/16/2025 Advisory disclosed
09/16/2025 +0 days CVE reserved
09/16/2025 +0 days VulDB entry created
01/16/2026 +122 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2023-53299 (🔒)
GCVE (CVE): GCVE-0-2023-53299
GCVE (VulDB): GCVE-100-324389
CERT Bund: WID-SEC-2025-2053 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 09/16/2025 14:12
Updated: 01/16/2026 08:26
Changes: 09/16/2025 14:12 (58), 12/03/2025 04:12 (11), 01/02/2026 13:22 (7), 01/11/2026 11:20 (1), 01/16/2026 08:26 (2)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!