CVE-2024-7883· NVD / CVE Program· CNA Arm

CMSE secure state may leak from stack to floating-point registers

Noroxi assessment

Priority: Monitor (action score 14/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.46% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
Fixed version: Arm Ltd Arm Compiler for Embedded 6.23; Arm Ltd CLang 20.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Arm Ltd Arm Compiler for Embedded 6.23; Arm Ltd CLang 20 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

When using Arm Cortex-M Security Extensions (CMSE), Secure stack contents can be leaked to Non-secure state via floating-point registers when a Secure to Non-secure function call is made that returns a floating-point value and when this is the first use of floating-point since entering Secure state. This allows an attacker to read a limited quantity of Secure stack contents with an impact on confidentiality. This issue is specific to code generated using LLVM-based compilers.

LowCVSS 3.7 · v3.1—No exploit Fix available

Pre-auth

Published: Oct 31, 2024
Updated: Jun 17, 2026
EPSS: 0.5% · 39th percentile
CWE: CWE-226

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 14 / 40 · 3.7 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.5%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · Arm: 3.7; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi 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 help

Affected 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
arm	arm compiler for embedded	cpe:2.3:a:arm:arm_compiler_for_embedded
arm	arm compiler for embedded fusa	cpe:2.3:a:arm:arm_compiler_for_embedded_fusa
arm	arm compiler for functional safety	cpe:2.3:a:arm:arm_compiler_for_functional_safety
arm	clang	cpe:2.3:a:arm:clang

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

arm arm compiler for embedded6.6 and later · before 6.23
arm arm compiler for embedded fusa6.16
arm arm compiler for embedded fusa6.21
arm arm compiler for functional safety6.6
arm clang11.0.0 and later · before 20.1.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Arm). Independent of NVD's CPE analysis and usually ahead of it.

Arm Ltd Arm Compiler for Embedded
- 6.6 and later · up to and including 6.22affected · semverfixed in 6.23
Arm Ltd Arm Compiler for Embedded FuSa 6.16LTS
- All versionsaffected
Arm Ltd Arm Compiler for Embedded FuSa 6.21
- All versionsaffected
Arm Ltd Arm Compiler for Functional Safety 6.6
- All versionsaffected
Arm Ltd CLang
- 13 and later · up to and including 19affected · semverfixed in 20

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	llvm-toolchain-14	all versions	—
Debian:12	llvm-toolchain-15	all versions	—
Debian:12	llvm-toolchain-16	all versions	—
Debian:12	llvm-toolchain-19	all versions	—
Debian:13	llvm-toolchain-17	all versions	—
Debian:13	llvm-toolchain-18	all versions	—

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
Arm Ltd Arm Compiler for Embedded	6.23	Vendor (CNA)
Arm Ltd CLang	20	Vendor (CNA)

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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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 researchers

Finders, 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.

No nightly-computed relations.

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