LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53184: arm64/sme: Set new vector length before reallocating

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel bug in ARM64 SME/SVE state handling. When a task changes vector length, the kernel can allocate a buffer using the old size, leaving it too small and risking memory corruption. The public record does not provide CVSS, CWE, or confirmed exploitation.

Executive priority

Treat as a kernel memory-corruption issue with uncertain severity. Prioritize normal kernel update governance for ARM64 systems, especially infrastructure using newer ARM features, but do not classify it as emergency without exploitation or CVSS evidence.

Technical view

In arm64 SME/SVE vector length changes, SVE state reallocation occurred before storing the new vector length in the task structure. Allocation could therefore use the old length, creating an undersized buffer and possible memory corruption. The fix moves the vector-length update before allocation.

Likely exposure

Exposure appears limited to Linux systems using ARM64 SME/SVE vector-length handling. The source lists Linux kernel commits and versions 6.1.42 and 6.4.7, but does not provide complete distro-specific affected ranges.

Exploitation context

The source bundle does not identify active exploitation, and KEV status is false. The kernel description says the issue triggered often after merge into mainline, but that is test/runtime instability evidence, not exploitation evidence.

Researcher notes

The key condition is ordering during vector-length changes: allocation used stale task metadata. The record lacks CVSS, CWE, proof of exploitability, and complete affected ranges, so validation should focus on commit presence and vendor backport status.

Mitigation direction

  • Check Linux vendor advisories for affected ARM64 kernel builds.
  • Update to a kernel containing the referenced stable fixes or vendor backports.
  • Prioritize ARM64 fleets that expose SME/SVE-capable hardware.
  • Track distro package advisories because affected range evidence is incomplete.

Validation and detection

  • Inventory ARM64 Linux systems and kernel package versions.
  • Confirm whether vendor kernels include the referenced upstream stable commits.
  • Review crash or memory-corruption telemetry on ARM64 hosts.
  • Document exceptions where SME/SVE hardware or kernel support is absent.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-53184 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxaa5cf8bd1318b6e7d500668b318c07a71cde783b, 292f0453b0d021bb1d3f64648bfdfca093512214, d4d5be94a87872421ea2569044092535aff0b886unaffected
LinuxLinux6.1.42, 6.4.7unaffected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.