All reports
Medium

kernel: arm64/sme: Set new vector length before reallocating

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2023-53184

Probability of exploitation in the next 30 days: 0.17%

FIRST EPSS · 2026-11-18

Description

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.

A flaw was found in the Linux kernel's Scalable Matrix Extension (SME) support on arm64 architectures. When a process modifies the vector length, memory is reallocated before the new length is recorded, resulting in an undersized buffer. A local attacker can exploit this flaw to cause memory corruption, which may lead to a Denial of Service (DoS) via a kernel crash or potentially allow privilege escalation.