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

Published Feb 29, 2024
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

arm64/sme: Always exit smealloc() early with existing storage

The Linux kernel CVE team has assigned CVE-2024-26618 to this issue.

Upstream advisory: https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-50-lee@kernel.org/T

Other sources

In the Linux kernel, the following vulnerability has been resolved:

arm64/sme: Always exit smealloc() early with existing storage

When smealloc() 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 smefree() themselves.

— NVD

Affected Software

9 affected componentsFixes available
redhat/kernel<6.6.15
6.6.15
redhat/kernel<6.7.3
6.7.3
redhat/kernel<6.8
6.8
Linux Linux kernel>=6.5<6.6.15
Linux Linux kernel>=6.7<6.7.3
debian/linux<6.1.140-1
6.1.140-1
debian/linux<6.6.15-1
6.6.15-1
debian/linux<6.6.15-1
6.6.15-1
debian/linux
6.1.176-16.1.190-16.12.107-16.12.115-27.2.12-17.2.15-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/kernel to a version that resolves this vulnerability.

    Fixed in 6.6.15
  2. Upgrade

    Upgrade redhat/kernel to a version that resolves this vulnerability.

    Fixed in 6.7.3
  3. Upgrade

    Upgrade redhat/kernel to a version that resolves this vulnerability.

    Fixed in 6.8
  4. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.140-1
  5. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.6.15-1
  6. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.115-2Fixed in 7.2.12-1Fixed in 7.2.15-1

Event History

Feb 29, 2024
CVE Published
via MITRE·03:52 PM
Data Sourced
via MITRE·03:52 PM
Description
Mar 11, 2024
Data Sourced
via NVD·06:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·06:15 PM
DescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2024-26618?

CVE-2024-26618 has been categorized by the Linux kernel CVE team, but severity ratings may vary based on specific use cases.

2

How do I fix CVE-2024-26618?

To mitigate CVE-2024-26618, update your kernel to versions 6.6.15, 6.7.3, or 6.8 for Red Hat systems, or ensure you are running appropriate Debian kernel versions.

3

Which systems are affected by CVE-2024-26618?

CVE-2024-26618 affects certain versions of the Linux kernel across both Red Hat and Debian distributions.

4

What is the cause of CVE-2024-26618?

CVE-2024-26618 is caused by an issue in the Linux kernel related to the handling of memory allocation in the ARM64 SMEm (Scalable Matrix Engine) architecture.

5

Has CVE-2024-26618 been resolved?

Yes, CVE-2024-26618 has been resolved in the latest kernel updates from the affected distributions.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203