exynos_2200 vulnerabilities

CVEs whose affected-version data names the exynos_2200 package. Each record lists the affected and patched versions; check a specific version with the dependency checker or POST /api/sbom.

exynos_2200 vulnerabilities

In the NAS message handler, improper validation of the length field in NAS message causes memory corruption

In the baseband, memory corruption during NAS packet processing can cause a denial of service.

Out of bound access in PPC due to race condition in global variable access

In the NR RRC component, improper handling of messages before authentication triggers a data abort, which leads to a denial‑of‑service condition.

Improper handling of messages before AS security activation can cause unexpected behavior

In the Samsung Exynos NPU driver, improper validation of user input in the ioctl handler can lead to an out-of-bounds write, which causes a denial of service.

In the Samsung Exynos NPU kernel driver, an integer overflow allows an unprivileged application to trigger memory corruption.

Insufficient validation of length fields in the GNSS firmware loader can result in kernel‑memory corruption.

Memory corruption in GPU driver due to improper validation of VMID reservation.

In the Samsung Exynos GPU driver, improper synchronization during buffer object creation and closing can lead to memory corruption

Improper handling of NAS DLTransport messages may lead to a baseband crash.

In the LTE RRC component, improper handling of messages before authentication triggers a data abort, which leads to a denial‑of‑service condition.

In the NAS Authentication Request message decoding procedure, a missing lower bound check causes an infinite loop, leading to Denial of Service.

Processing a malformed RRC Reconfiguration message leads to an out-of-bounds (OOB) access, resulting in a denial-of-service (DoS) condition.

Continuously sending control‑plane messages causes the baseband to crashes.