CVE-2023-53313
BaseFortify
Publication date: 2025-09-16
Last updated on: 2025-12-01
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 2.6.33 (inc) to 4.14.322 (exc) |
| linux | linux_kernel | From 4.15 (inc) to 4.19.291 (exc) |
| linux | linux_kernel | From 4.20 (inc) to 5.4.251 (exc) |
| linux | linux_kernel | From 5.5 (inc) to 5.10.188 (exc) |
| linux | linux_kernel | From 5.11 (inc) to 5.15.121 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.1.39 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.3.13 (exc) |
| linux | linux_kernel | From 6.4 (inc) to 6.4.4 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-NVD-CWE-noinfo |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel's md/raid10 component involves a lack of input validation when setting the max_read_errors parameter. Specifically, there is no check on the input value when echoing to md/max_read_errors, which can lead to an overflow and incorrect setting of max_corr_read_errors. The issue has been fixed by adding input validation to prevent overflow.
How can this vulnerability impact me? :
The vulnerability could cause incorrect behavior in the RAID10 subsystem of the Linux kernel due to overflow in the max_read_errors setting. This might lead to improper error handling or data corruption in RAID10 arrays, potentially affecting system stability or data integrity.