Re: Snapdragon X65 baseband buffer overflow - potential for mass device DoS

[Intergalactic Auditor via NANOG <nanog () lists nanog org>]

Update: Baseband firmware trace analysis confirms buffer overflow, not just array index issue.

Evidence from Jan 10 crash:
- Explicit "!OVERFLOW!" marker in baseband trace (offset 0x00013365)
- Watchdog reset: "rst wdog,6vdt_in_1" 
- Crash recovery: "gcb_crash_wakeup"
- SDMState active at crash time

Corrected flow: SDM transition → buffer overflow in baseband firmware → memory corruption → firmware deadlock → 
watchdog timeout → forced reboot

Same trigger pattern on Jan 10, 11, 14. CWE-120 (Buffer Overflow)



On Friday, January 16th, 2026 at 10:21 PM, Intergalactic Auditor via NANOG <nanog () lists nanog org> wrote:

> Disclosing for the NOCs at war everyday.
>
> Buffer overflow in Qualcomm X65 baseband
>
> Issue: SDM state transition → unchecked array index → baseband deadlock → forced reboot
> Timeline: 9ms to error, 2.3s to crash
> Trigger: Potentially via 5G/satellite signal
>
> Observed events:
> 2026-01-10, 01-11, 01-14 ~06:00 EST
>
> Monitor for:
> - Clustered device crash reports in narrow time window
> - "No Service" complaints with normal network metrics
> - Baseband watchdog resets (rst wdog)
>
> Technical: https://github.com/0verdu/X65_BufferOverflow
> Contact: Keybase: justthemessenger
> _______________________________________________
> NANOG mailing list
> https://lists.nanog.org/archives/list/nanog () lists nanog org/message/P5Q6URQC7YWXBUUWTWA5RREUPZH3B2QE/
_______________________________________________
NANOG mailing list 
https://lists.nanog.org/archives/list/nanog () lists nanog org/message/YJNBWSGFW2VSEAOKXEL5SMWLYDQIBZII/