5.5
MEDIUM CVSS 3.1
CVE-2024-26618
arm64/sme: Always exit sme_alloc() early with existing storage
Description

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.

INFO

Published Date :

March 11, 2024, 6:15 p.m.

Last Modified :

May 22, 2025, 1:15 p.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2024-26618 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Linux linux_kernel
CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 3.1 MEDIUM [email protected]
Solution
This vulnerability can be remediated by updating the Linux kernel packages.
  • Update the affected Linux kernel packages.
  • Reboot the system after updating the kernel.
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2024-26618 is associated with the following CWEs:

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2024-26618 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2024-26618 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    May. 22, 2025

    Action Type Old Value New Value
    Added Reference https://git.kernel.org/stable/c/f6421555dbd7cb3d4d70b69f33f998aaeca1e3b5
  • Initial Analysis by [email protected]

    Feb. 14, 2025

    Action Type Old Value New Value
    Added CVSS V3.1 NIST AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
    Added CWE NIST CWE-770
    Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.5 up to (excluding) 6.6.15 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.7.3
    Changed Reference Type https://git.kernel.org/stable/c/569156e4fa347237f8fa2a7e935d860109c55ac4 No Types Assigned https://git.kernel.org/stable/c/569156e4fa347237f8fa2a7e935d860109c55ac4 Mailing List, Patch
    Changed Reference Type https://git.kernel.org/stable/c/569156e4fa347237f8fa2a7e935d860109c55ac4 No Types Assigned https://git.kernel.org/stable/c/569156e4fa347237f8fa2a7e935d860109c55ac4 Mailing List, Patch
    Changed Reference Type https://git.kernel.org/stable/c/814af6b4e6000e574e74d92197190edf07cc3680 No Types Assigned https://git.kernel.org/stable/c/814af6b4e6000e574e74d92197190edf07cc3680 Mailing List, Patch
    Changed Reference Type https://git.kernel.org/stable/c/814af6b4e6000e574e74d92197190edf07cc3680 No Types Assigned https://git.kernel.org/stable/c/814af6b4e6000e574e74d92197190edf07cc3680 Mailing List, Patch
    Changed Reference Type https://git.kernel.org/stable/c/dc7eb8755797ed41a0d1b5c0c39df3c8f401b3d9 No Types Assigned https://git.kernel.org/stable/c/dc7eb8755797ed41a0d1b5c0c39df3c8f401b3d9 Mailing List, Patch
    Changed Reference Type https://git.kernel.org/stable/c/dc7eb8755797ed41a0d1b5c0c39df3c8f401b3d9 No Types Assigned https://git.kernel.org/stable/c/dc7eb8755797ed41a0d1b5c0c39df3c8f401b3d9 Mailing List, Patch
  • CVE Modified by af854a3a-2127-422b-91ae-364da2661108

    Nov. 21, 2024

    Action Type Old Value New Value
    Added Reference https://git.kernel.org/stable/c/569156e4fa347237f8fa2a7e935d860109c55ac4
    Added Reference https://git.kernel.org/stable/c/814af6b4e6000e574e74d92197190edf07cc3680
    Added Reference https://git.kernel.org/stable/c/dc7eb8755797ed41a0d1b5c0c39df3c8f401b3d9
  • CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    May. 29, 2024

    Action Type Old Value New Value
  • CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    May. 14, 2024

    Action Type Old Value New Value
  • CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Mar. 11, 2024

    Action Type Old Value New Value
    Added Description 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.
    Added Reference Linux https://git.kernel.org/stable/c/569156e4fa347237f8fa2a7e935d860109c55ac4 [No types assigned]
    Added Reference Linux https://git.kernel.org/stable/c/814af6b4e6000e574e74d92197190edf07cc3680 [No types assigned]
    Added Reference Linux https://git.kernel.org/stable/c/dc7eb8755797ed41a0d1b5c0c39df3c8f401b3d9 [No types assigned]
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
Vulnerability Scoring Details
Base CVSS Score: 5.5
Attack Vector
Attack Complexity
Privileges Required
User Interaction
Scope
Confidentiality Impact
Integrity Impact
Availability Impact