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
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.
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 Authentication Request message decoding procedure, a missing lower bound check causes an infinite loop, leading to Denial of Service.
In the LTE RRC component, improper handling of messages before authentication triggers a data abort, which leads to a denial‑of‑service condition.
Insufficient validation of length fields in the GNSS firmware loader can result in kernel‑memory corruption.
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.
Processing a malformed RRC message leads to an out-of-bounds read, resulting in a denial-of-service condition.