Baseband Crash from Unauthenticated RRC Setup Messages
Incorrect handling of unauthenticated downlink RRC Setup messages can cause the baseband to crash
Incorrect handling of unauthenticated downlink RRC Setup messages can cause the baseband to crash
A memory corruption vulnerability caused by improper validation of messages
Processing a malformed RRC Reconfiguration message leads to an out-of-bounds (OOB) access, resulting in a denial-of-service (DoS) condition.
Improper handling of NAS DLTransport messages may lead to a baseband crash.
An attacker may send a malicious IMS message to the target device, potentially leading to information exposure through the SIP message flow.
In the NR RRC component, improper handling of messages before authentication triggers a data abort, which leads to a denial‑of‑service condition.
Incorrect handling of SIP packets leads to baseband crashes
In IMS stack, improper handling of SIP packets leads to Incorrect_Access_Control vulnerability
In the Exynos modem's IMS stack, improper handling of SDP payload 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 Service.
Insufficient length validation in the GNSS firmware loader may lead to corruption of kernel memory.
Improper handling of messages before AS security activation can cause unexpected behavior
In the baseband, memory corruption during NAS packet processing can cause a denial of service.
In the NAS message handler, improper validation of the length field in NAS message causes memory corruption
Continuously sending control‑plane messages causes the baseband to crashes.
In the Exynos modem's IMS stack, Out of Bound access occurs due to improper validation.
Processing a malformed RRC message leads to an out-of-bounds read, resulting in a denial-of-service condition.