Arm Vulnerabilities

Timeline

The analysis of the timeline helps to identify the required approach and handling of single items and item collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Prioritizing items becomes possible.

Type

The moderation team is working with the threat intelligence team to categorize software that is affected by security vulnerabilities. This helps to illustrate the assignment of these categories to determine the most affected software types.

Product

ARM Mali GPU Kernel Driver14
Arm Valhall GPU Kernel Driver13
Arm 5th Gen GPU Architecture Kernel Driver11
Arm Bifrost GPU Kernel Driver10
ARM Mbed OS9

Grouping vulnerabilities by products helps to get an overview. This makes it possible to determine an homogeneous landscape or the most important hotspots in heterogeneous landscapes.

Remediation

Official Fix56
Temporary Fix0
Workaround0
Unavailable0
Not Defined53

Vendors and researchers are eager to find countermeasures to mitigate security vulnerabilities. These can be distinguished between multiple forms and levels of remediation which influence risks differently.

Exploitability

High9
Functional0
Proof-of-Concept5
Unproven0
Not Defined95

Researcher and attacker which are looking for security vulnerabilities try to exploit them for academic purposes or personal gain. The level and quality of exploitability can be distinguished to determine simplicity and strength of attacks.

Access Vector

Not Defined0
Physical0
Local34
Adjacent44
Network31

The approach a vulnerability it becomes important to use the expected access vector. This is typically via the network, local, or physically even.

Authentication

Not Defined0
High1
Low81
None27

To exploit a vulnerability a certail level of authentication might be required. Vulnerabilities without such a requirement are much more popular.

User Interaction

Not Defined0
Required1
None108

Some attack scenarios require some user interaction by a victim. This is typical for phishing, social engineering and cross site scripting attacks.

C3BM Index

Our unique C3BM Index (CVSSv3 Base Meta Index) cumulates the CVSSv3 Meta Base Scores of all entries over time. Comparing this index to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

CVSSv3 Base

≤10
≤20
≤36
≤49
≤57
≤629
≤719
≤828
≤911
≤100

The Common Vulnerability Scoring System (CVSS) is an industry standard to define the characteristics and impacts of security vulnerabilities. The base score represents the intrinsic aspects that are constant over time and across user environments. Our unique meta score merges all available scores from different sources to aggregate to the most reliable result.

CVSSv3 Temp

≤10
≤20
≤37
≤48
≤59
≤630
≤718
≤830
≤97
≤100

The Common Vulnerability Scoring System (CVSS) uses temp scores to reflect the characteristics of a vulnerability that may change over time but not across user environments. This includes reporting confidence, exploitability and remediation levels. We do also provide our unique meta score for temp scores, even though other sources rarely publish them.

VulDB

≤10
≤20
≤37
≤411
≤56
≤645
≤74
≤835
≤91
≤100

The moderation team is always defining the base vector and base score for an entry. These and all other available scores are used to generate the meta score.

NVD

≤10
≤20
≤30
≤45
≤52
≤610
≤74
≤823
≤910
≤105

The National Vulnerability Database (NVD) is also defining CVSS vectors and scores. These are usually not complete and might differ from VulDB scores.

CNA

≤10
≤20
≤30
≤42
≤50
≤64
≤71
≤89
≤98
≤102

A CVE Numbering Authority (CNA) is responsible for assigning new CVE entries. They might also include a CVSS score. These are usually not complete and might differ from VulDB scores.

Vendor

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

Some vendors are willing to publish their own CVSS vectors and scores for vulnerabilities in their products. The coverage varies from vendor to vendor.

Research

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

There are sometimes also security researcher which provide their own CVSS vectors and scores for vulnerabilities they have found and published.

Exploit 0-day

<1k23
<2k47
<5k39
<10k0
<25k0
<50k0
<100k0
≥100k0

The moderation team is working with the threat intelligence team to determine prices for exploits. Our unique algorithm is used to identify the 0-day prices for an exploit, before it got distributed or became public. Calculated prices are aligned to prices disclosed by vulnerability broker and compared to prices we see on exploit markets.

Exploit Today

<1k89
<2k15
<5k5
<10k0
<25k0
<50k0
<100k0
≥100k0

The 0-day prices do not consider time-relevant factors. The today price does reflect price impacts like disclosure of vulnerability details, alternative exploits, availability of countermeasures. These dynamic aspects might decrease the exploit prices over time. Under certain circumstances this happens very fast.

Exploit Market Volume

Our unique calculation of exploit prices makes it possible to forecast the expected exploit market volume. The calculated prices for all possible 0-day expoits are cumulated for this task. Comparing the volume to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

🔴 CTI Activities

Our unique Cyber Threat Intelligence aims to determine the ongoing research of actors to anticipiate their acitivities. Observing exploit markets on the Darknet, discussions of vulnerabilities on mailinglists, and exchanges on social media makes it possible to identify planned attacks. Monitored actors and activities are classified whether they are offensive or defensive. They are also weighted as some actors are well-known for certain products and technologies. And some of their disclosures might contain more or less details about technical aspects and personal context. The world map highlights active actors in real-time.

Affected Products (81): 5th Gen GPU Architecture (1), 5th Gen GPU Architecture Kernel Driver (16), 5th Gen GPU Architecture Userspace Driver (1), 8-M (1), 8-M Security Extensions Requirements on Development Tools (1), AArch64cryptolib (1), Android-NN-Driver (1), Armv8-A Core (1), Bifrost (4), Bifrost GPU Kernel Driver (14), Bifrost GPU Userspace Driver (1), CLang (1), CMSIS RTOS2 (1), CPU (1), China STAR-MC (1), Compiler (1), Compiler 5 (2), Compiler 5, Compiler 6, Compiler for Embedded, Compiler for Embedded FuSa, Compiler for Linux, Development Studio, Development Studio Morello Edition, Forge, Mobile Studio, DS-5 Development Studio, Fast Models, GNU Toolchain, Installer Vulnerabilities, Keil MDK, Socrates (1), Compiler 6 (2), Compiler for Embedded (3), Compiler for Embedded FuSa (3), Compiler for Functional Safety (1), Compiler for Linux (2), Cortex (1), Cortex-78C (1), Cortex-A72 (1), Cortex-A73 (1), Cortex-A75 (1), Cortex-A77 (1), Cortex-A78 (1), Cortex-A78AE (1), Cortex-A710 (1), Cortex-M33 (1), Cortex-M35P (1), Cortex-M55 (1), Cortex-X1 (1), Cortex-X1C (1), Cortex-X2 (1), Cortex-X3 (2), Cortex-X4 (2), Cortex-X925 (2), DS-5 Development Studio (2), Development Studio (2), Development Studio Morello Edition (2), Fast Models (2), Forge (2), GNU Toolchain (2), Gralloc Module (1), Installer Vulnerabilities (2), Keil MDK (2), Mali GPU Driver (5), Mali GPU Kernel Driver (14), Mali Kernel Driver (1), Mbed OS (9), Mbed TLS (9), Midgard (4), Midgard GPU Kernel Driver (4), Midgard GPU Userspace Driver (1), Mobile Studio (2), Neoverse (1), Neoverse N2 (1), Neoverse V1 (1), Neoverse V2 (2), Neoverse V3 (2), Neoverse V3AE (2), SCP-Firmware (3), Socrates (2), Travis (1), TrustZone CryptoCell 310 (1), Trusted Firmware (5), Trusted Firmware-A (1), Trusted Firmware-M (3), Valhall (5), Valhall GPU (1), Valhall GPU Kernel Driver (19), Valhall GPU Userspace Driver (1), astcenc (2), mbed (1), mbed-ualloc (1), mbed TLS (7), mbedTLS (2)

PublishedBaseTempVulnerabilityProdExpRemEPSSCTICVE
02/03/20257.87.5Arm Valhall GPU Kernel Driver use after freeHardware Driver SoftwareNot DefinedOfficial Fix0.000430.06CVE-2025-0015
02/03/20255.75.5Arm Bifrost GPU Kernel Driver infinite loopHardware Driver SoftwareNot DefinedOfficial Fix0.000430.03CVE-2024-6790
01/28/20252.52.5Arm Cortex-X925 value delimitersUnknownNot DefinedNot Defined0.000430.06CVE-2024-7881
01/22/20255.55.3ARM Cortex-A72/Cortex-A73/Cortex-A75 Privilege EscalationUnknownNot DefinedOfficial Fix0.000430.02CVE-2024-10929
01/14/20255.75.7Arm SCP-Firmware SCMI Message exceptional conditionFirmware SoftwareNot DefinedNot Defined0.000430.02CVE-2024-11864
01/14/20255.75.7Arm SCP-Firmware SCMI Message exceptional conditionFirmware SoftwareNot DefinedNot Defined0.000430.06CVE-2024-11863
12/10/20247.27.2ARM Cortex-A77 Hardware Page Aggregation exposure of resourceUnknownNot DefinedNot Defined0.000430.08CVE-2024-5660
11/13/20248.08.0ARM SCP-Firmware transport_message_handler exceptional conditionFirmware SoftwareNot DefinedNot Defined0.000430.06CVE-2024-9413
10/31/20243.73.7Arm Compiler for Embedded Function Call sensitive information in resource not removed before reuseUnknownNot DefinedNot Defined0.000430.05CVE-2024-7883
09/03/20247.87.6Arm Bifrost GPU Kernel Driver use after freeHardware Driver SoftwareNot DefinedOfficial Fix0.000430.00CVE-2024-3655
08/05/20247.87.8Arm Bifrost GPU Kernel Driver use after freeHardware Driver SoftwareNot DefinedNot Defined0.000510.02CVE-2024-2937
08/05/20247.87.8Arm Bifrost GPU Kernel Driver use after freeHardware Driver SoftwareNot DefinedNot Defined0.000510.00CVE-2024-4607
07/01/20247.87.8Arm Valhall GPU/5th Gen GPU Architecture memory corruptionUnknownNot DefinedNot Defined0.000430.00CVE-2024-0153
06/07/20247.77.7Arm Bifrost GPU Kernel Driver use after freeHardware Driver SoftwareHighNot Defined0.158620.04CVE-2024-4610
05/03/20247.87.8Arm 5th Gen GPU Architecture Kernel Driver use after freeHardware Driver SoftwareNot DefinedNot Defined0.000430.00CVE-2024-1395
05/03/20247.87.8Arm Valhall GPU Kernel Driver use after freeHardware Driver SoftwareNot DefinedNot Defined0.000430.03CVE-2023-6363
05/03/20247.87.8Arm Bifrost GPU Kernel Driver use after freeHardware Driver SoftwareNot DefinedNot Defined0.000430.03CVE-2024-1067
04/24/20245.04.9ARM v8-M Security Extensions Requirements on Development Tools unexpected data typeUnknownNot DefinedOfficial Fix0.000430.03CVE-2024-0151
04/19/20246.36.1ARM Mbed OS hciTrSerialRxIncoming buffer overflowUnknownNot DefinedNot Defined0.000450.06CVE-2024-22905
04/19/20247.87.8Arm Bifrost GPU Kernel Driver use after freeHardware Driver SoftwareNot DefinedNot Defined0.000430.03CVE-2024-1065
04/19/20247.87.8ARM Midgard GPU Kernel Driver use after freeHardware Driver SoftwareNot DefinedNot Defined0.000430.00CVE-2024-0671
03/04/20247.47.4ARM Midgard GPU Kernel Driver use after freeHardware Driver SoftwareNot DefinedNot Defined0.000510.06CVE-2023-6241
03/04/20247.77.7ARM Midgard GPU Kernel Driver use after freeHardware Driver SoftwareNot DefinedNot Defined0.000430.00CVE-2023-6143
02/05/20245.75.6Arm Bifrost GPU Kernel Driver use after freeHardware Driver SoftwareNot DefinedOfficial Fix0.000510.00CVE-2023-5249
02/05/20246.66.5Arm Bifrost GPU Kernel Driver out-of-bounds writeHardware Driver SoftwareNot DefinedOfficial Fix0.000510.00CVE-2023-5643

84 more entries are not shown

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!