Samsung Semiconductor vulnerabilities
Every vulnerability this feed holds for Samsung Semiconductor, merged from five public registers and ordered by what warrants attention first — exploited in the wild, then CVSS, then recency.
35 vulnerabilities tracked.
- — Insufficient length validation in the GNSS firmware loader may lead to corruption of kernel memory.
- — In the Samsung GPU driver, improper reference count handling during command submission can lead to memory corruption.
- — In the Samsung Exynos GPU driver, improper synchronization during buffer object creation and closing can lead to memory corruption
- — Out-of-bounds memory access in a device driver due to improper resource state tracking.
- — Memory corruption in GPU driver due to improper validation of VMID reservation.
- — Incorrect authorization in Samsung framework services due to missing permission checks
- — A double free vulnerability in NPU driver due to improper pointer management (940)
- — A double free vulnerability in NPU driver due to improper pointer management (941)
- — In the Samsung Exynos ENN NeuralNetworks HAL, improper input validation during request processing can cause memory corruption and lead to a…
- — In the Samsung Exynos H-Arx DRM plugin, improper input validation during buffer operations can cause memory corruption, potentially leading…
- — Integer overflow in NPU driver parameter processing due to insufficient bounds checking.
- — In the Exynos NPU driver, improper validation of user input in the ioctl handler can lead to an out-of-bounds write, which causes a denial…
- — Insufficient validation of length fields in the GNSS firmware loader can result in kernel‑memory corruption.
- — In IMS stack, improper handling of SIP packets leads to IncorrectAccessControl vulnerability
- — A memory corruption vulnerability caused by improper validation of messages
- — In the Exynos modem's IMS stack, improper handling of SDP payload leads to a Denial of Service
- — In the Samsung Exynos NPU kernel driver, an integer overflow allows an unprivileged application to trigger memory corruption.
- — Improper permission handling during buffer operations allows untrusted applications to create memory mappings with inappropriate permissions
- — Improper handling of messages before AS security activation can cause unexpected behavior
- — Out of bound access in PPC due to race condition in global variable access
- — Processing a malformed RRC message leads to an out-of-bounds read, resulting in a denial-of-service condition.
- — In the baseband, memory corruption during NAS packet processing can cause a denial of service.
- — In the NR RRC component, improper handling of messages before authentication triggers a data abort, which leads to a denial‑of‑service…
- — In the NAS message handler, improper validation of the length field in NAS message causes 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…
- — An attacker may send a malicious IMS message to the target device, potentially leading to information exposure through the SIP message flow.
- — In the Exynos modem's IMS stack, Out of Bound access occurs due to improper validation.
- — In the NAS Authentication Request message decoding procedure, a missing lower bound check causes an infinite loop, leading to Denial of…
- — In the LTE RRC component, improper handling of messages before authentication triggers a data abort, which leads to a 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.
- — Incorrect handling of SDP payload leads to a Denial of Service
- — Improper handling of NAS DLTransport messages may lead to a baseband crash.
- — Incorrect handling of unauthenticated downlink RRC Setup messages can cause the baseband to crash
- — Continuously sending control‑plane messages causes the baseband to crashes.
- — Incorrect handling of SIP packets leads to baseband crashes
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 Samsung Semiconductor is free of vulnerabilities.
Query this from an agent over MCP · Check a lockfile by version
Other vendors tracked here
Google Red Hat Microsoft Apple zephyrproject Apache Software Foundation n/a Hewlett Packard Enterprise (HPE) MediaTek, Inc. Linux Tanium Eclipse Foundation Unknown FreeRDP IBM Dell Oracle Corporation MONGODB Gitea WAVLINK kyverno vercel vim Hitachi