vciy

CVE-2022-40762

INDEX BUILT · 2026-10-18

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

A Memory Allocation with Excessive Size Value vulnerablity in the TEE_Realloc function in Samsung mTower through 0.3.0 allows a trusted application…

CVE-2022-407623 of 4 sources documented this
21

rank 21 = 0 + 19 + 0 + 2 + 0

rank@v1 · backlog

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.01009  ·  without this subject the record ranks 21

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 7.5, from NVD  ·  without this subject the record ranks 2

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 21

How much of the world it touches

NVD CPE configurations

1 product in the CPE ranges  ·  without this subject the record ranks 19

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 21

Hindsight · the state

0.01009EPSSNOT IN KEVas of 2026-10-18
Severity7.5 HIGHreceipt
Harmunauthenticated · networkreceipt
Exploitationnone in held sources
Defenseno fix version held
Movementsteadyreceipt
PLATEAU10Minimal movement since 2022-09-17, 1477 days at 0.01, as of 2026-10-03. arc-rules@v1

Foresight · where to check next

This record is one instance of CWE-770, allocation of resources without limits or throttling. The index holds 2602 prior instances of this class, 2 KEV-listed. taxonomy@v1

Full pattern panel

Color is a claim, not decoration:the hostile worldthe defenseno signal

Check a version against this record

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (free with an account: one stack of three products)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

Patch by…

Or open an investigation: an incident or a near miss on this CVE, kept with its evidence where anyone in your organisation can find it.

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · no privileges required · no user interaction · low attack complexityreceipt
ImpactComplete availability lossreceipt
Scored fromCVSS v3.1 · NVD's vectorreceipt
Weakness classCWE-770 Allocation of Resources Without Limits or Throttlingreceipt
Published consequencesCWE-770: Availability: DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory), DoS: Resource Consumption (Other)cwe-consequences@4.20

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed inNo fix version in held sources, as the index stood on 3 Oct 2026.
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.
BOD 26-04 deadlineIf the system is reachable from the internet: 14 days. If not: fix at the next system upgrade.derived
Show full BOD 26-04 deadline

CISA has not scored it, so the directive's own defaults apply: automatable no, technical impact total. Calendar days from the KEV listing or from when you find it on a system, whichever is first. Federal agencies are bound from 7 Dec 2026, and contracts often carry it to suppliers. The directive and its table

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, NVD7.5 HIGHreceipt
Exploit probability0.01009 · top 38% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned bymitrereceipt
Recorded changes22 · last 18 Oct 2026derived

Affected & Fixed Versions as published

Named in the CPE rangesSamsung mtowerreceipt
Published rangessamsung mtower <= 0.3.0receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$30,800over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$30,800 = $4.99M incident cost x 0.6121449559255632 exposure x 0.01009 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

A Memory Allocation with Excessive Size Value vulnerablity in the TEE_Realloc function in Samsung mTower through 0.3.0 allows a trusted application to trigger a Denial of Service (DoS) by invoking the function TEE_Realloc with an excessive number for the parameter len. receipt

NVD's analysis a second authority

severity
7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
weakness
CWE-770
affected versions
samsung mtower <= 0.3.0

check it yourself github.com github.com receipt

Movement the material steps

17 Sep 20220.00885
7 Mar 20234.6e-4 · scoring model v2023.03.01
17 Mar 20250.00082 · scoring model v2025.03.14
15 Jun 20260.00802 · scoring model v2026.06.15
3 Oct 20260.01009
Show all 22 observations
17 Sep 20220.00885
7 Mar 20234.6e-4
8 Mar 20230.00046
17 Aug 20230.00065
23 Sep 20230.00067
27 Feb 20240.00074
8 Apr 20240.00105
26 Oct 20240.00149
17 Mar 20250.00082
29 Mar 20250.00118
30 Mar 20250.00082
11 Jun 20250.00103
13 Jul 20250.0011
18 Sep 20250.00492
22 Sep 20250.0038
12 Mar 20260.004
15 Jun 20260.00802
27 Jun 20260.00839
17 Jul 20260.0087
22 Aug 20260.00887
14 Sep 20260.01002
3 Oct 20260.01009

22 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.01009Published2022-09-16Index as of2026-10-03

The record had been public for 4 years when this index was last written.

Published 2022-09-16 receipt · Index as of 2026-10-03 derived

The pattern, elsewhere

This record is one instance of CWE-770, allocation of resources without limits or throttling. The index holds 2602 prior instances of this class, 2 KEV-listed. cwe-consequences@4.20

CVE-2020-3566 · Cisco IOS XR Softwarematches 7 of 8KEV listed · 2020receipt
CVE-2020-3569 · Cisco IOS XR Softwarematches 7 of 8KEV listed · 2020receipt

2602 records in this class held. The six above are ranked by exploit maturity, then recency.

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2022-40762.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.