LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26618: arm64/sme: Always exit sme_alloc() early with existing storage

In the Linux kernel, the following vulnerability has been resolved: arm64/sme: Always exit sme_alloc() early with existing storage When sme_alloc() is called with existing storage and we are not flushing we will always allocate new storage, both leaking the existing storage and corrupting the state. Fix this by separating the checks for flushing and for existing storage as we do for SVE. Callers that reallocate (eg, due to changing the vector length) should call sme_free() themselves.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel flaw affects ARM64 SME handling. Under specific conditions, the kernel can allocate new SME storage when storage already exists, leaking memory and corrupting internal state. The public record does not provide CVSS, CWE, or confirmed real-world exploitation, so urgency should be based on whether affected ARM64 Linux kernels are in use.

Executive priority

Treat this as a targeted kernel maintenance item, not an emergency based on available evidence. Prioritize affected ARM64 fleets and managed Linux images, especially where kernel stability and isolation are operationally important.

Technical view

The issue is in arm64/sme sme_alloc(). When called with existing storage and not flushing, it allocates fresh storage instead of returning early, causing a leak and state corruption. The fix separates flushing checks from existing-storage checks, matching the SVE pattern. Kernel stable fix commits are referenced by the CVE source bundle.

Likely exposure

Exposure appears limited to Linux systems running affected ARM64 kernel versions with SME-related kernel code present. The bundle lists Linux kernel versions including 6.5, 6.1.140, 6.6.15, 6.7.3, and 6.8 as affected. Distribution backports may change version-based conclusions.

Exploitation context

The supplied sources do not show CISA KEV inclusion, public exploitation, exploit code, or attacker prerequisites. The described impact is memory leakage and kernel state corruption, but business impact is not quantified in the public record.

Researcher notes

Evidence is sparse: no CVSS, CWE, exploit status, or detailed trigger path is included. Analysis should stay close to upstream commit metadata and distro advisories. Avoid assuming broad x86 exposure because the issue is specifically under arm64/sme.

Mitigation direction

  • Apply vendor kernel updates that include the linked stable fixes.
  • Prioritize ARM64 Linux systems using affected kernel branches.
  • For Debian LTS, review and apply the referenced Debian security update.
  • Reboot systems into the patched kernel after update.
  • If no vendor advisory exists, track upstream stable kernel guidance.

Validation and detection

  • Inventory ARM64 Linux hosts and running kernel versions.
  • Compare kernels against vendor advisories and the CVE affected-version data.
  • Confirm installed kernels include one of the referenced stable fixes or vendor backports.
  • Verify systems rebooted into the updated kernel, not only installed it.
  • Document exceptions where vendor status remains unclear.
Prepared
Confidence
medium
Sources
7

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-2024-26618 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
2ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux21614ba60883eb93b99a7ee4b41cb927f93b39ae, 5d0a8d2fba50e9c07cde4aad7fba28c008b07a5b, 5d0a8d2fba50e9c07cde4aad7fba28c008b07a5b, 5d0a8d2fba50e9c07cde4aad7fba28c008b07a5b, e01af8e26c23a08625a3dd6c8c472a1752d76cce, 6.1.47, 6.4.12unaffected
LinuxLinux6.5, 0, 6.1.140, 6.6.15, 6.7.3, 6.8affected
Weakness

CWE details

No CWE listed

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