CVE-2023-53380
BaseFortify
Publication date: 2025-09-18
Last updated on: 2025-12-11
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| 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-476 | The product dereferences a pointer that it expects to be valid but is NULL. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a null pointer dereference in the Linux kernel's RAID10 synchronization function (raid10_sync_request). It occurs because two separate checks on a variable 'mreplace' are inconsistent: the first sets a flag 'need_replace' and uses 'mreplace' if it is not faulty, while the second sets 'mreplace' to NULL if it is faulty but does not update 'need_replace'. If the 'Faulty' condition changes between these checks, a null pointer dereference can happen. The fix merges the two checks and replaces 'need_replace' with 'mreplace' to ensure consistency.
How can this vulnerability impact me? :
This vulnerability can cause a null pointer dereference in the Linux kernel RAID10 synchronization process, which may lead to a kernel crash or system instability. This can result in denial of service or potential data loss on systems using RAID10 configurations.