Race to Charge: Concurrency Bugs and State Integrity Violations in EV...
summary
Manual audit and sanitizer-assisted experiments on Everest Core version 2025.12.1 uncover 11 concurrency vulnerabilities now issued as 11 CVEs, including eight inconsistent-locking bugs and three state-integrity violations that enable persistent unauthorized charging, authorization-withdrawal bypass, and DoS via memory corruption. Reproduction uses TSan/ASan/UBSan and a two-thread harness; one race is replayed on Raspberry Pi 4. Root causes are inconsistent locking, non-atomic state transitions, and missing async validation; exploits demonstrate the failures in real event interleavings.
AI-written summary · about
related talks
31mProtecting the Attack Surface and Data Silos of an EV Charging Network
17mHotWire: Real-World Impersonation and Discharge Attacks on Electric Vehicle Charging...
11mShort: Breaking the Charge: Exploiting State Manipulation in EV Charging
54mCLKscrew: Exposing The Perils of Security-Oblivious Energy Management
01h 16mClassic Vulnerabilities
01h 05mTheory and Security
34mExploiting Race Conditions Using the Scheduler
42mUnderstanding Data Races in the Linux Kernel