[BUG] Antigravity LS Crash: “CRNGT failed” on AMD Zen+ (BoringSSL/RDRAND conflict)

Google Antigravity
1

Environment: Arch Linux, AMD ryzen 3450u mobile, AGESA/Microcode Revision 0x0810810e (2025/2026 mitigation).

1 --- KERNEL ---
2 Linux 6.18.13-arch1-1 x86_64
3
4 --- CPU ---
5 Vendor ID: AuthenticAMD
6 Model: AMD Ryzen 5 3450U with Radeon Vega Mobile Gfx
7 Microcode Revision: 0x0810810e
8
9 --- BINARY ---
10 Path: /usr/lib/antigravity/extensions/antigravity/bin/language_server_linux_x64
11 Type: ELF 64-bit LSB pie executable, dynamically linked (libc only)
12 Symbols: BoringCrypto/FIPS enabled
13
14 — REPRODUCTION —
15 getrandom(…) = 8
16 CRNGT failed.
17 SIGABRT: abort

Issue:
The Antigravity Language Server (language_server_linux_x64) crashes immediately on startup with CRNGT failed. SIGABRT: abort.

Technical Root Cause:

  1. Broken Hardware RNG: Recent Zen+ firmware updates “disable” RDRAND/RDSEED by forcing them to return constant values (all zeros)
    while still setting the success flag.
  2. FIPS Enforcement: The binary is statically linked with BoringSSL in FIPS mode.
  3. CRNGT Failure: BoringSSL performs a “Continuous Random Number Generator Test.” Receiving consecutive identical blocks from the
    hardware triggers a security abort.
  4. Kernel Bypass: The binary executes raw assembly RDRAND instructions, ignoring Linux kernel parameters like nordrand or clearcpuid.

Impact:
The IDE is completely non-functional on patched AMD systems as the Language Server cannot initialize.

Confirmed Workaround:
Force a software entropy fallback by masking hardware capabilities at the library level:
export OPENSSL_ia32cap=“0:0”

Requested Fix:
Update the BoringSSL implementation or the Go toolchain to detect “poisoned” hardware RNG data and fallback gracefully, or provide a
non-FIPS binary for Linux distributions where hardware security mitigations are active.

2

Hi @AshutoshSononey ,

Thanks for providing the community workaround.
Thank you for your feedback. We appreciate you taking the time to share your thoughts with us, and we’ll be filing a fix.

1 Like