CVE-2024-26618: arm64/sme: Always exit sme_alloc() early with existing storage
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 569156e4fa347237f8fa2a7e935d860109c55ac4, 6.1.140, 6.5.
Low priority for now. Upgrade to Linux Linux 569156e4fa347237f8fa2a7e935d860109c55ac4, 6.1.140, 6.5 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Mar 11, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- CWE-770
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.5 and later · before 6.6.15
- linux linux kernel6.7 and later · before 6.7.3
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- e01af8e26c23a08625a3dd6c8c472a1752d76cce, 6.5affected
- 21614ba60883eb93b99a7ee4b41cb927f93b39ae and later · before f6421555dbd7cb3d4d70b69f33f998aaeca1e3b5affected · git
- 5d0a8d2fba50e9c07cde4aad7fba28c008b07a5b and later · before 569156e4fa347237f8fa2a7e935d860109c55ac4affected · git
- 5d0a8d2fba50e9c07cde4aad7fba28c008b07a5b and later · before 814af6b4e6000e574e74d92197190edf07cc3680affected · git
- 5d0a8d2fba50e9c07cde4aad7fba28c008b07a5b and later · before dc7eb8755797ed41a0d1b5c0c39df3c8f401b3d9affected · git
- 6.1.47 and later · before 6.1.140affected · semver
- 6.4.12 and later · before 6.5affected · semver
- before 6.5not affected · semver
- 6.1.140 and later · up to and including 6.1.*not affected · semver
- 6.6.15 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:11 | linux-6.1 | before 6.1.140-1~deb11u1 | 6.1.140-1~deb11u1 |
| Debian:12 | linux | before 6.1.140-1 | 6.1.140-1 |
| Debian:13 | linux | before 6.6.15-1 | 6.6.15-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-26616Mar 11, 2024 · btrfs: scrub: avoid use-after-free when chunk length is not 64K aligned31Monitor
- ← EarlierCVE-2024-26617Mar 11, 2024 · fs/proc/task_mmu: move mmu notification mechanism inside mm lock28Monitor
- Later →CVE-2024-26619Mar 11, 2024 · riscv: Fix module loading free order31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 569156e4fa347237f8fa2a7e935d860109c55ac4 | Vendor (CNA) |
| Linux Linux | 6.1.140 | Vendor (CNA) |
| Linux Linux | 6.5 | Vendor (CNA) |
| Linux Linux | 814af6b4e6000e574e74d92197190edf07cc3680 | Vendor (CNA) |
| Linux Linux | dc7eb8755797ed41a0d1b5c0c39df3c8f401b3d9 | Vendor (CNA) |
| Linux Linux | f6421555dbd7cb3d4d70b69f33f998aaeca1e3b5 | Vendor (CNA) |
| debian:linux | 6.1.140-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.1 | 6.1.140-1~deb11u1 · Debian:11 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2021-4713714 days apartnet: lantiq: fix memory corruption in RX ring39Monitor
- CVE-2024-3596970 days apartipv6: fix race condition between ipv6_get_ifaddr and ipv6_del_addr35Monitor
- CVE-2021-4755174 days apartdrm/amd/amdkfd: Fix kernel panic when reset failed and been triggered again31Monitor
- CVE-2024-34027105 days apartf2fs: compress: fix to cover {reserve,release}_compress_blocks() w/ cp_rwsem lock31Monitor
- CVE-2021-471304 days apartnvmet: fix freeing unallocated p2pmem30Monitor
- CVE-2023-525299 days apartHID: sony: Fix a potential memory leak in sony_probe()24Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-770 · Allocation of Resources Without Limits or ThrottlingCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- FloodingCAPEC-125likelihood: High · Medium
- Excessive AllocationCAPEC-130likelihood: Medium · Medium
- XML Ping of the DeathCAPEC-147likelihood: Low · Medium
- Exponential Data ExpansionCAPEC-197likelihood: High · Medium
- Serialized Data Parameter BlowupCAPEC-229likelihood: High · High
- Serialized Data with Nested PayloadsCAPEC-230likelihood: Medium · High
- Oversized Serialized Data PayloadsCAPEC-231likelihood: Medium · High
- HTTP DoSCAPEC-469Low
ATT&CK techniques
- Network Denial of Service:Direct Network FloodT1498.001
- Network Denial of Service:Reflection AmplificationT1498.002
- Endpoint Denial of ServiceT1499
- Endpoint Denial of Service: OS Exhaustion FloodT1499.001
- Endpoint Denial of Service:Service Exhaustion FloodT1499.002
- Endpoint Denial of Service:Application Exhaustion FloodT1499.003
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.