Exynos 2200 vulnerabilities and CVEs
Known vulnerabilities affecting Exynos 2200, with exploit availability attached to each one, so you can tell a flaw someone has written code for from one nobody has.
15 vulnerabilities tracked.
- — 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
- — In the NAS message handler, improper validation of the length field in NAS message causes memory corruption
- — In the NR RRC component, improper handling of messages before authentication triggers a data abort, which leads to a denial‑of‑service…
- — 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
- — Improper handling of messages before AS security activation can cause unexpected behavior
- — In the Samsung Exynos NPU kernel driver, an integer overflow allows an unprivileged application to trigger memory corruption.
- — 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…
- — Processing a malformed RRC Reconfiguration message leads to an out-of-bounds (OOB) access, resulting in a denial-of-service (DoS) condition.
- — In the LTE RRC component, improper handling of messages before authentication triggers a data abort, which leads to a denial‑of‑service…
- — In the NAS Authentication Request message decoding procedure, a missing lower bound check causes an infinite loop, leading to Denial of…
- — Continuously sending control‑plane messages causes the baseband to crashes.
- — Improper handling of NAS DLTransport messages may lead to a baseband crash.
What this covers
This feed accumulates forward from the day it started storing records, and a name search that finds nothing here is also looked up against the registers directly — so an older advisory resolves even when it predates the corpus. It is still a reading view, not a substitute for the vendor's own advisory, and absence from this page is not a statement that Exynos 2200 is free of vulnerabilities.
Query this from an agent over MCP · Check a lockfile by version
Other products tracked here
Chrome Red Hat Enterprise Linux 9 macOS Red Hat Enterprise Linux 8 Red Hat Enterprise Linux 10 Zephyr Android Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support Windows Server 2022 iOS and iPadOS Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions Windows 11 version 26H1 Windows 11 Version 24H2 Windows Server 2025 Windows 11 Version 25H2 Windows Server 2025 (Server Core installation) Windows Server 2019 (Server Core installation) Windows Server 2019 Windows 10 Version 21H2 Red Hat Enterprise Linux 9.6 Extended Update Support Windows 10 Version 1809 Windows 10 Version 22H2 Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions