Answer in brief
CVE-2023-53184 records a High severity (CVSS 7.8) vulnerability in arm64/sme: Set new vector length before reallocating. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:6.1.42:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.4.7:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.5:rc3:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=aa5cf8bd1318b6e7d500668b318c07a71cde783b <356e711640aea6ed145da9407499388b45264cb4 || >=292f0453b0d021bb1d3f64648bfdfca093512214 <807ada0e4aa3c9090c66009a99fa530c462012c9 || >=d4d5be94a87872421ea2569044092535aff0b886 <05d881b85b48c7ac6a7c92ce00aa916c4a84d052 | 356e711640aea6ed145da9407499388b45264cb4, 807ada0e4aa3c9090c66009a99fa530c462012c9, 05d881b85b48c7ac6a7c92ce00aa916c4a84d052 |
| Linux/Linuxgeneric | >=6.1.42 <6.1.43 || >=6.4.7 <6.4.8 | 6.1.43, 6.4.8 |
Published upstream
Sep 15, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: arm64/sme: Set new vector length before reallocating As part of fixing the allocation of the buffer for SVE state when changing SME vector length we introduced an immediate reallocation of the SVE state, this is also done when changing the SVE vector length for consistency. Unfortunately this reallocation is done prior to writing the new vector length to the task struct, meaning the allocation is done with the old vector length and can lead to memory corruption due to an undersized buffer being used. Move the update of the vector length before the allocation to ensure that the new vector length is taken into account. For some reason this isn't triggering any problems when running tests on the arm64 fixes branch (even after repeated tries) but is triggering issues very often after merge into mainline.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2023-53184 records a High severity (CVSS 7.8) vulnerability in arm64/sme: Set new vector length before reallocating. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:6.1.42:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.4.7:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.5:rc3:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=aa5cf8bd1318b6e7d500668b318c07a71cde783b <356e711640aea6ed145da9407499388b45264cb4 || >=292f0453b0d021bb1d3f64648bfdfca093512214 <807ada0e4aa3c9090c66009a99fa530c462012c9 || >=d4d5be94a87872421ea2569044092535aff0b886 <05d881b85b48c7ac6a7c92ce00aa916c4a84d052 | 356e711640aea6ed145da9407499388b45264cb4, 807ada0e4aa3c9090c66009a99fa530c462012c9, 05d881b85b48c7ac6a7c92ce00aa916c4a84d052 |
| Linux/Linuxgeneric | >=6.1.42 <6.1.43 || >=6.4.7 <6.4.8 | 6.1.43, 6.4.8 |
Published upstream
Sep 15, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: arm64/sme: Set new vector length before reallocating As part of fixing the allocation of the buffer for SVE state when changing SME vector length we introduced an immediate reallocation of the SVE state, this is also done when changing the SVE vector length for consistency. Unfortunately this reallocation is done prior to writing the new vector length to the task struct, meaning the allocation is done with the old vector length and can lead to memory corruption due to an undersized buffer being used. Move the update of the vector length before the allocation to ensure that the new vector length is taken into account. For some reason this isn't triggering any problems when running tests on the arm64 fixes branch (even after repeated tries) but is triggering issues very often after merge into mainline.
Quoted source text, attributed separately from HOL analysis.