Home/CVE/Inconsistent data in instruction and data cache when creating wasm code could lead to a potentially exploitable crash.<b
CVE
CVE-2022-40957
Inconsistent data in instruction and data cache when creating wasm code could lead to a potentially exploitable crash.<b
Inconsistent data in instruction and data cache when creating wasm code could lead to a potentially exploitable crash.<br>This bug only affects Firefox on ARM64 platforms.. This vulnerability affects Firefox ESR < 102.3, Thunderbird < 102.3, and Firefox < 105.
MEDIUM · CVSS 6.5
EPSS 0.01082
EPSS exploitation odds1.08% · top 38%
Monitor
- No active-exploitation, high-EPSS, or public-exploit signals - routine patching cadence
Sigma rules1
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2022-40957, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
↗
Exploitation momentum
484 days of EPSSdormant
Flat and low - no real exploitation pressure. This reads the direction and speed of EPSS over time, which can move before EPSS itself peaks or before CISA lists it.
EPSS exploitation probability
1.08%
Top 38%odds of exploitation in the next 30 days
CVSS metric silhouette
shape grows toward worst-case
SSVC triage · cisa-vulnrichment
Exploitation
none
Automatable
no
Tech impact
partial
CVSS vector breakdown
Exploitability - how they get in
Attack Vector
Network
Adjacent
Local
Physical
Attack Complexity
Low
High
Privileges Required
None
Low
High
User Interaction
None
Required
Scope
Unchanged
Changed
Impact - what breaks
Confidentiality
None
Low
High
Integrity
None
Low
High
Availability
None
Low
High
VECTOR
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:HLifecycle
- 22 Dec 2022Published to NVD
- 17 Jun 2026Last modified
Every entry is a recorded date - NVD publish/modify, CISA KEV add, public exploit disclosure. No inferred events.
Attack path
Full kill chain
◆
ATT&CK techniques
2Techniques this CVE enables. Pills with a solid outline are high confidence - named directly in ATT&CK or Nuclei, or human-curated by CTID; the rest are inferred from the weakness type using MITRE's CVE Mapping Methodology and the CWE → CAPEC chain. Broad, generic-weakness guesses are filtered out. A small N× marks a technique that N independent sources agree on.
▤ Build a SIEM detection for these techniques⬡
Weakness Classification
▤
Affected Products & Versions
3▤
Affected Packages
4Language-ecosystem packages (from OSV) tied to this CVE, with the version that fixes it - the dependency-level detail NVD doesn’t carry.
AlmaLinux:8
firefox
fixed in 102.3.0-6.el8_6.alma
AlmaLinux:8
thunderbird
fixed in 102.3.0-3.el8_6.alma
AlmaLinux:9
firefox
fixed in 102.3.0-6.el9_0.alma
AlmaLinux:9
thunderbird
fixed in 102.3.0-3.el9_0.alma
▤
Related CVEs
8CVEs linked to this one by a shared weakness (CWE) or affected product - joins on data already in the engine, with the reason shown per row.
CVE-2021-31890
A vulnerability has been identified in Capital Embedded AR Classic 431-422 (All ...
same CWE-240
HIGH
CVE-2023-39914
NLnet Labs' bcder library up to and including version 0.7.2 panics while decodin...
same CWE-240
HIGH
CVE-2023-39915
NLnet Labs' Routinator up to and including version 0.12.1 may crash when trying ...
same CWE-240
HIGH
CVE-2025-4321
In a Bluetooth device, using RS9116-WiseConnect SDK experiences a Denial of Serv...
same CWE-240
CVE-2002-2436
The Cascading Style Sheets (CSS) implementation in Mozilla Firefox before 4.0, T...
same product
CVE-2002-2437
The JavaScript implementation in Mozilla Firefox before 4.0, Thunderbird before ...
same product
CVE-2003-1492
Netscape Navigator 7.0.2 and Mozilla allows remote attackers to access cookie in...
same product
CVE-2004-0648
Mozilla (Suite) before 1.7.1, Firefox before 0.9.2, and Thunderbird before 0.7.2...
1
same product
📦
Fixed versions by distribution
16The package version that resolves this CVE on each Linux distribution, from the vendor’s published security data. fixed in shows a patched version exists; open means the package is listed as affected with no fix yet.
alpine v3.19firefox-esr fixed in 102.3.0-r0
alpine v3.20firefox-esr fixed in 102.3.0-r0
oracle allfirefox fixed in 0:102.3.0-6.0.1.el7_9
oracle allthunderbird open
rhel 8firefox fixed in 0:102.3.0-6.el8_6
rhel 8thunderbird open
rhel 9firefox open
rhel 9thunderbird open
suse sle15MozillaFirefox fixed in 0:102.3.0-150000.150.59.2
suse sle15MozillaFirefox-branding-SLE fixed in 0:102-150200.9.10.1
suse sle15MozillaFirefox-devel fixed in 0:102.3.0-150000.150.59.2
suse sle15MozillaFirefox-translations-common fixed in 0:102.3.0-150200.152.61.1
suse sle15MozillaFirefox-translations-other fixed in 0:102.3.0-150200.152.61.1
suse sle15MozillaThunderbird fixed in 0:102.4.0-150200.8.85.1
suse sle15MozillaThunderbird-translations-common fixed in 0:102.4.0-150200.8.85.1
suse sle15MozillaThunderbird-translations-other fixed in 0:102.4.0-150200.8.85.1
◈
Sigma Hunt Rules
1Exact rules name this CVE ID. Product rules name an affected product in their title. Related rules cover techniques used by actors who exploited this CVE. Showing the most relevant matches; the complete related set is on the full drill-down.
⚑
Vendor Advisories
29suse-csafopenSUSE-SU-2024:14572-1
suse-csafopenSUSE-SU-2024:12358-1
suse-csafopenSUSE-SU-2024:12398-1
suse-csafopenSUSE-SU-2024:12425-1
usnUSN-5724-1
suse-csafSUSE-SU-2022:3800-1
usnUSN-5649-1
suse-csafSUSE-SU-2022:3440-1
suse-csafSUSE-SU-2022:3441-1
suse-csafSUSE-SU-2022:3396-1
suse-csafrhsa-2022_6700
suse-csafrhsa-2022_6702
suse-csafrhsa-2022_6708
suse-csafrhsa-2022_6710
suse-csafrhsa-2022_6711
suse-csafrhsa-2022_6717
mozilla-mfsaMFSA2022-40
🔗
References & Sources
4Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.