Modern cars are rolling data centers, and yet almost no one gets to look under the hood of the software side. The Cadillac Lyriq — GM's flagship electric SUV — runs a substantial Linux-based infotainment and vehicle-services stack layered over a mix of proprietary automotive middleware. This post appears to kick off a series where the author documents the reconnaissance phase of rooting one: identifying attack surfaces, mapping the boards and buses, and figuring out where the seams are before ever writing an exploit.

Why this matters for a technical audience:

• Automotive security is chronically underexamined. Compared to phones or consoles, cars get very little independent scrutiny — and the ones that do get scrutinized (Tesla, older ICE ECUs) already have big research communities. A serious writeup on a GM EV is genuinely rare.
• "Lay of the Land" posts are the most useful part of any hardware hacking series. Later posts show the flashy exploit; the first post teaches you how to think about an unfamiliar embedded target — reading FCC filings, spotting debug headers, identifying SoCs from silkscreen, guessing at IPC boundaries between the IVI and the vehicle CAN gateway.
• Right-to-repair and ownership implications. As cars increasingly ship features behind subscription paywalls (heated seats, acceleration boosts, remote start), rooting work is arguably the only path to genuine ownership of the hardware you paid $60K+ for.
• The threat model is genuinely interesting. Automotive stacks have to reconcile hard-real-time safety domains (brakes, steering) with soft consumer-electronics domains (Spotify, Android Auto). Watching a researcher probe the boundary between those is a masterclass in defense-in-depth architecture — and its failure modes.

The blog is on a small personal domain with no comments and one HN upvote, which usually signals either a niche audience or a post that hasn't found its people yet. Given the appetite on HN for Tesla teardowns, John Deere jailbreaks, and iPod/Kindle rooting sagas, this one is almost certainly the latter — it just posted at the wrong time of day.

If part 2 delivers actual UART pinouts and firmware dumps, this could become a canonical reference for GM IVI research.