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