← Back

Arm

arm

193 CVEs • 141 products

Products (141)

Click to collapse
Toggle
Mbed Tls
mbed_tls
Mbed Os
mbed-os
Cortex A
cortex-a
Mbed
mbed
Tf Psa Crypto
tf-psa-crypto
Mbed Crypto
mbed_crypto
Arm Compiler
arm_compiler
Scp Firmware
scp_firmware
Cortex A72
cortex-a72
Fast Models
fast_models
Cortex R
cortex-r
Mbed Mqtt
mbed-mqtt
Mbed Coap
mbed-coap
Cmsis Rtos
cmsis-rtos
Mbed Ualloc
mbed_ualloc
Gnu Toolchain
gnu_toolchain
Keil Mdk
keil_mdk
Linaro Forge
linaro_forge
Mbed Studio
mbed_studio
Clang
clang
Cortex R7
cortex-r7
Cortex R8
cortex-r8
Cortex A8
cortex-a8
Cortex A9
cortex-a9
Cortex A12
cortex-a12
Cortex A15
cortex-a15

CVEs (193)

CVE
VENDORS
PRODUCTS
UPDATED
PUBLISHED
CVSS
1Arm
1Arm Development Studio
Jun 17, 2026
Jul 22, 2025
N/A· v4
5.9 MEDIUM· v3
N/A· v2
Uncontrolled Search Path Element in Arm Development Studio before 2025 may allow an attacker to perform a DLL hijacking attack. Successful exploitation could lead to local arbitrary code execution in the context of the u...Show more
Uncontrolled Search Path Element in Arm Development Studio before 2025 may allow an attacker to perform a DLL hijacking attack. Successful exploitation could lead to local arbitrary code execution in the context of the user running Arm Development Studio.Show less
2Arm
Trustedfirmware
2Mbed Tls
Mbed Tls
Jun 17, 2026
Jul 20, 2025
N/A· v4
3.7 LOW· v3
N/A· v2
In Mbed TLS 3.6.1 through 3.6.3 before 3.6.4, a timing discrepancy in block cipher padding removal allows an attacker to recover the plaintext when PKCS#7 padding mode is used.
1Arm
1Mbed Tls
Jun 17, 2026
Jul 20, 2025
N/A· v4
9.8 CRITICAL· v3
N/A· v2
Mbed TLS before 3.6.4 allows a use-after-free in certain situations of applications that are developed in accordance with the documentation. The function mbedtls_x509_string_to_names() takes a head argument that is docum...Show more
Mbed TLS before 3.6.4 allows a use-after-free in certain situations of applications that are developed in accordance with the documentation. The function mbedtls_x509_string_to_names() takes a head argument that is documented as an output argument. The documentation does not suggest that the function will free that pointer; however, the function does call mbedtls_asn1_free_named_data_list() on that argument, which performs a deep free(). As a result, application code that uses this function (relying only on documented behavior) is likely to still hold pointers to the memory blocks that were freed, resulting in a high risk of use-after-free or double-free. In particular, the two sample programs x509/cert_write and x509/cert_req are affected (use-after-free if the san string contains more than one DN).Show less
1Arm
1Mbed Tls
Jun 17, 2026
Jul 20, 2025
N/A· v4
7.5 HIGH· v3
N/A· v2
Mbed TLS before 3.6.4 has a NULL pointer dereference because mbedtls_asn1_store_named_data can trigger conflicting data with val.p of NULL but val.len greater than zero.
1Arm
1Mbed Tls
Jun 17, 2026
Jul 4, 2025
N/A· v4
4.8 MEDIUM· v3
N/A· v2
Mbed TLS before 3.6.4 has a PEM parsing one-byte heap-based buffer underflow, in mbedtls_pem_read_buffer and two mbedtls_pk_parse functions, via untrusted PEM input.
1Arm
1Mbed Tls
Jun 17, 2026
Jul 4, 2025
N/A· v4
7.8 HIGH· v3
N/A· v2
Mbed TLS before 3.6.4 has a race condition in AESNI detection if certain compiler optimizations occur. An attacker may be able to extract an AES key from a multithreaded program, or perform a GCM forgery.
2Arm
Trustedfirmware
2Mbed Tls
Mbed Tls
Jun 17, 2026
Jul 4, 2025
N/A· v4
6.5 MEDIUM· v3
N/A· v2
In MbedTLS 3.3.0 before 3.6.4, mbedtls_lms_import_public_key does not check that the input buffer is at least 4 bytes before reading a 32-bit field, allowing a possible out-of-bounds read on truncated input. Specifically...Show more
In MbedTLS 3.3.0 before 3.6.4, mbedtls_lms_import_public_key does not check that the input buffer is at least 4 bytes before reading a 32-bit field, allowing a possible out-of-bounds read on truncated input. Specifically, an out-of-bounds read in mbedtls_lms_import_public_key allows context-dependent attackers to trigger a crash or limited adjacent-memory disclosure by supplying a truncated LMS (Leighton-Micali Signature) public-key buffer under four bytes. An LMS public key starts with a 4-byte type indicator. The function mbedtls_lms_import_public_key reads this type indicator before validating the size of its input.Show less
2Arm
Trustedfirmware
2Mbed Tls
Mbed Tls
Jun 17, 2026
Jul 4, 2025
N/A· v4
4.9 MEDIUM· v3
N/A· v2
In MbedTLS 3.3.0 before 3.6.4, mbedtls_lms_verify may accept invalid signatures if hash computation fails and internal errors go unchecked, enabling LMS (Leighton-Micali Signature) forgery in a fault scenario. Specifical...Show more
In MbedTLS 3.3.0 before 3.6.4, mbedtls_lms_verify may accept invalid signatures if hash computation fails and internal errors go unchecked, enabling LMS (Leighton-Micali Signature) forgery in a fault scenario. Specifically, unchecked return values in mbedtls_lms_verify allow an attacker (who can induce a hardware hash accelerator fault) to bypass LMS signature verification by reusing stale stack data, resulting in acceptance of an invalid signature. In mbedtls_lms_verify, the return values of the internal Merkle tree functions create_merkle_leaf_value and create_merkle_internal_value are not checked. These functions return an integer that indicates whether the call succeeded or not. If a failure occurs, the output buffer (Tc_candidate_root_node) may remain uninitialized, and the result of the signature verification is unpredictable. When the software implementation of SHA-256 is used, these functions will not fail. However, with hardware-accelerated hashing, an attacker could use fault injection against the accelerator to bypass verification.Show less
1Arm
35th Gen Gpu Architecture Userspace Driver
Bifrost Gpu Userspace DriverValhall Gpu Userspace Driver
Jun 17, 2026
Jun 2, 2025
N/A· v4
7.8 HIGH· v3
N/A· v2
Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerability in Arm Ltd Bifrost GPU Userspace Driver, Arm Ltd Valhall GPU Userspace Driver, Arm Ltd Arm 5th Gen GPU Architecture Userspace Driver a...Show more
Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerability in Arm Ltd Bifrost GPU Userspace Driver, Arm Ltd Valhall GPU Userspace Driver, Arm Ltd Arm 5th Gen GPU Architecture Userspace Driver allows a non-privileged user process to perform valid GPU processing operations, including via WebGL or WebGPU, to access outside of buffer bounds.This issue affects Bifrost GPU Userspace Driver: from r18p0 through r49p3, from r50p0 through r51p0; Valhall GPU Userspace Driver: from r28p0 through r49p3, from r50p0 through r54p0; Arm 5th Gen GPU Architecture Userspace Driver: from r41p0 through r49p3, from r50p0 through r54p0.Show less
1Arm
35th Gen Gpu Architecture Kernel Driver
Bifrost Gpu Kernel DriverValhall Gpu Kernel Driver
Jun 17, 2026
Jun 2, 2025
N/A· v4
7.8 HIGH· v3
N/A· v2
Use After Free vulnerability in Arm Ltd Bifrost GPU Kernel Driver, Arm Ltd Valhall GPU Kernel Driver, Arm Ltd Arm 5th Gen GPU Architecture Kernel Driver allows a local non-privileged user process to perform valid GPU mem...Show more
Use After Free vulnerability in Arm Ltd Bifrost GPU Kernel Driver, Arm Ltd Valhall GPU Kernel Driver, Arm Ltd Arm 5th Gen GPU Architecture Kernel Driver allows a local non-privileged user process to perform valid GPU memory processing operations to gain access to already freed memory.This issue affects Bifrost GPU Kernel Driver: from r44p0 through r49p3, from r50p0 through r51p0; Valhall GPU Kernel Driver: from r44p0 through r49p3, from r50p0 through r54p0; Arm 5th Gen GPU Architecture Kernel Driver: from r44p0 through r49p3, from r50p0 through r54p0.Show less
1Arm
25th Gen Gpu Architecture Kernel Driver
Valhall Gpu Kernel Driver
Jun 17, 2026
Jun 2, 2025
N/A· v4
7.8 HIGH· v3
N/A· v2
Use After Free vulnerability in Arm Ltd Valhall GPU Kernel Driver, Arm Ltd Arm 5th Gen GPU Architecture Kernel Driver allows a local non-privileged user process to perform improper GPU memory processing operations to gai...Show more
Use After Free vulnerability in Arm Ltd Valhall GPU Kernel Driver, Arm Ltd Arm 5th Gen GPU Architecture Kernel Driver allows a local non-privileged user process to perform improper GPU memory processing operations to gain access to already freed memory.This issue affects Valhall GPU Kernel Driver: from r53p0 before r54p0; Arm 5th Gen GPU Architecture Kernel Driver: from r53p0 before r54p0.Show less
1Arm
35th Gen Gpu Architecture Kernel Driver
Bifrost Gpu Kernel DriverValhall Gpu Kernel Driver
Jun 17, 2026
May 2, 2025
N/A· v4
7.8 HIGH· v3
N/A· v2
Use After Free vulnerability in Arm Ltd Bifrost GPU Kernel Driver, Arm Ltd Valhall GPU Kernel Driver, Arm Ltd Arm 5th Gen GPU Architecture Kernel Driver allows a local non-privileged user process to perform valid GPU pro...Show more
Use After Free vulnerability in Arm Ltd Bifrost GPU Kernel Driver, Arm Ltd Valhall GPU Kernel Driver, Arm Ltd Arm 5th Gen GPU Architecture Kernel Driver allows a local non-privileged user process to perform valid GPU processing operations to gain access to already freed memory.This issue affects Bifrost GPU Kernel Driver: from r8p0 through r49p3, from r50p0 through r51p0; Valhall GPU Kernel Driver: from r19p0 through r49p3, from r50p0 through r53p0; Arm 5th Gen GPU Architecture Kernel Driver: from r41p0 through r49p3, from r50p0 through r53p0.Show less
1Arm
25th Gen Gpu Architecture Kernel Driver
Valhall Gpu Kernel Driver
Jun 17, 2026
May 2, 2025
N/A· v4
7.8 HIGH· v3
N/A· v2
Use After Free vulnerability in Arm Ltd Valhall GPU Kernel Driver, Arm Ltd Arm 5th Gen GPU Architecture Kernel Driver allows a local non-privileged user process to perform improper GPU memory processing operations to gai...Show more
Use After Free vulnerability in Arm Ltd Valhall GPU Kernel Driver, Arm Ltd Arm 5th Gen GPU Architecture Kernel Driver allows a local non-privileged user process to perform improper GPU memory processing operations to gain access to already freed memory. This issue affects Valhall GPU Kernel Driver: from r29p0 through r49p3, from r50p0 through r53p0; Arm 5th Gen GPU Architecture Kernel Driver: from r41p0 through r49p3, from r50p0 through r53p0.Show less
1Arm
35th Gen Gpu Architecture Userspace Driver
Bifrost Gpu Userspace DriverValhall Gpu Userspace Driver
Jun 17, 2026
Apr 7, 2025
N/A· v4
5.9 MEDIUM· v3
N/A· v2
Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerability in Arm Ltd Bifrost GPU Userspace Driver, Arm Ltd Valhall GPU Userspace Driver, Arm Ltd Arm 5th Gen GPU Architecture Userspace Driver a...Show more
Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerability in Arm Ltd Bifrost GPU Userspace Driver, Arm Ltd Valhall GPU Userspace Driver, Arm Ltd Arm 5th Gen GPU Architecture Userspace Driver allows a non-privileged user process to make valid GPU processing operations, including via WebGL or WebGPU, to access a limited amount outside of buffer bounds.This issue affects Bifrost GPU Userspace Driver: from r0p0 through r49p2, from r50p0 through r51p0; Valhall GPU Userspace Driver: from r19p0 through r49p2, from r50p0 through r53p0; Arm 5th Gen GPU Architecture Userspace Driver: from r41p0 through r49p2, from r50p0 through r53p0.Show less
2Arm
Trustedfirmware
2Mbed Tls
Mbed Tls
Jun 17, 2026
Mar 25, 2025
N/A· v4
4.8 MEDIUM· v3
N/A· v2
Mbed TLS before 2.28.10 and 3.x before 3.6.3, in some cases of failed memory allocation or hardware errors, uses uninitialized stack memory to compose the TLS Finished message, potentially leading to authentication bypas...Show more
Mbed TLS before 2.28.10 and 3.x before 3.6.3, in some cases of failed memory allocation or hardware errors, uses uninitialized stack memory to compose the TLS Finished message, potentially leading to authentication bypasses such as replays.Show less
2Arm
Trustedfirmware
2Mbed Tls
Mbed Tls
Jun 17, 2026
Mar 25, 2025
N/A· v4
5.4 MEDIUM· v3
N/A· v2
Mbed TLS before 2.28.10 and 3.x before 3.6.3, on the client side, accepts servers that have trusted certificates for arbitrary hostnames unless the TLS client application calls mbedtls_ssl_set_hostname.
1Arm
25th Gen Gpu Architecture Kernel Driver
Valhall Gpu Kernel Driver
Jun 17, 2026
Feb 3, 2025
N/A· v4
7.8 HIGH· v3
N/A· v2
Use After Free vulnerability in Arm Ltd Valhall GPU Kernel Driver, Arm Ltd Arm 5th Gen GPU Architecture Kernel Driver allows a local non-privileged user process to make improper GPU processing operations to gain access t...Show more
Use After Free vulnerability in Arm Ltd Valhall GPU Kernel Driver, Arm Ltd Arm 5th Gen GPU Architecture Kernel Driver allows a local non-privileged user process to make improper GPU processing operations to gain access to already freed memory.This issue affects Valhall GPU Kernel Driver: from r48p0 through r49p1, from r50p0 through r52p0; Arm 5th Gen GPU Architecture Kernel Driver: from r48p0 through r49p1, from r50p0 through r52p0.Show less
1Arm
35th Gen Gpu Architecture Kernel Driver
Bifrost Gpu Kernel DriverValhall Gpu Kernel Driver
Jun 17, 2026
Feb 3, 2025
N/A· v4
6.1 MEDIUM· v3
N/A· v2
Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability in Arm Ltd Bifrost GPU Kernel Driver, Arm Ltd Valhall GPU Kernel Driver, Arm Ltd Arm 5th Gen GPU Architecture Kernel Driver allows a non-privileged use...Show more
Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability in Arm Ltd Bifrost GPU Kernel Driver, Arm Ltd Valhall GPU Kernel Driver, Arm Ltd Arm 5th Gen GPU Architecture Kernel Driver allows a non-privileged user process to make valid GPU memory processing operations, including via WebGL or WebGPU, to cause the whole system to become unresponsive.This issue affects Bifrost GPU Kernel Driver: r44p1, from r46p0 through r49p0, from r50p0 through r51p0; Valhall GPU Kernel Driver: r44p1, from r46p0 through r49p0, from r50p0 through r51p0; Arm 5th Gen GPU Architecture Kernel Driver: r44p1, from r46p0 through r49p0, from r50p0 through r51p0.Show less
1Arm
9C1 Premium Firmware
C1 Pro FirmwareC1 Ultra Firmware+6 more
Jun 17, 2026
Jan 28, 2025
N/A· v4
5.1 MEDIUM· v3
N/A· v2
An unprivileged context can trigger a data memory-dependent prefetch engine to fetch the contents of a privileged location and consume those contents as an address that is also dereferenced.
1Arm
4Cortex A57 Firmware
Cortex A72 FirmwareCortex A73 Firmware+1 more
Jun 17, 2026
Jan 22, 2025
N/A· v4
5.1 MEDIUM· v3
N/A· v2
In certain circumstances, an issue in Arm Cortex-A57, Cortex-A72 (revisions before r1p0), Cortex-A73 and Cortex-A75 may allow an adversary to gain a weak form of control over the victim's branch history.