2003 Chevrolet Tahoe Lt, Super Clean, 144,000 Hwy Miles, 1 Owner on 2040-cars

Auto blog

Chevy might've pulled out of NASCAR if it weren't for new Gen 6 car

We've been on the fence with NASCAR for some time now. On one hand, it's some of the closest racing anywhere in motorsports, with actual passing and door-handle-to-door-handle action as a matter of course. But on the other, it's become template racing - a personality-driven sport more about the drivers than any sort of loyalty to a particular automaker. The Car Of Tomorrow format really rammed that message home, with a racecar's identity coming down to little more than headlamp stickers slapped on the nose. That's not necessarily a bad thing in and of itself, but we've wondered for some time what's in it for the automakers, who pay big money to stay in a series that has had little increasingly little do with street car sales, let alone innovation.
Apparently General Motors was beginning to wonder the same thing. In a new ESPN report, Rick Hendrick, team owner of Hendrick Motorsports, suggests that GM would have seriously considered leaving NASCAR if it wasn't for the move away from the COT to the new Gen 6 racer. According to Hendrick, GM North America boss Mark Reuss spearheaded the charge away from the 2007 COT and toward a racecar with clearer automaker ties - cars like the new Chevrolet SS racer shown above. Learn more about the fight for a closer-to-production look in the ESPN story at the link.
Now, if we could just get more rear-wheel drive V8 coupes into showrooms....

Chevy Corvette is latest car breached by hackers

UPDATE: This story has been updated with comment from General Motors. In the latest car-hacking exploit in a summer full of them, researchers from the University of California-San Diego say they've found a way to manipulate braking in a 2013 Chevrolet Corvette. The vulnerabilities may not be limited to that model. Cyber-security researchers breached the car's security systems via a device they had plugged into the Corvette's OBD-II port, and through that connection, they sent messages that could turn windshield wipers on and off and tamper with the brakes as the car drove at low speeds. It's the latest in a series of car hacks that involve access to critical systems obtained via the OBD-II port, where drivers can plug in devices that provide anything from diagnostic information for mechanics to driving information for insurance companies. Last November, cyber-security engineers from Argus Cyber Security remotely controlled vehicle functions in a car that had a OBD-II dongle called a Zubie installed. In January, researchers from Digital Bond Labs found security holes in an information-tracking dongle popular with more than 2 million Progressive Insurance customers. Those came before prominent hacks unveiled in recent weeks, in which researchers remotely commandeered control of a Jeep Cherokee and, separately, showcased problems with GM's OnStar infotainment system. Regarding the dongles that plug into the OBD-II ports, Stefan Savage, a Cal-San Diego professor involved in the research, tells WIRED that, "we acquired some of these things, reverse-engineered them, and along the way, found that they had a whole bunch of security deficiencies." Savage and others unveiled the latest study at the Usenix security conference Tuesday. In a video of their exploit entitled "Fast and Vulnerable," they show how they sent SMS messages from a smartphone to the dongle plugged into the car's OBD-II port. From there, their messages accessed the CAN bus, a network on the car that connects individual electronic control units, which control dozens of vehicle functions. As they send the commands to brake the car, the driver of the Corvette notes "the pedal doesn't react to any pressure." General Motors issued a written response Wednesday, warning drivers to be careful with third-party devices they plug into their OBD-II ports.

GM recalls 8,500 Chevrolet Malibu models for rear suspension glitch

According to a letter from General Motors to the National Highway Traffic Safety Administration, flaws in the build process of the 2013 Chevrolet Malibu have led to the recall of 8,519 cars. Units built between December 6, 2011 and January 15, 2013 may have been assembled with rear suspension cradles that had insufficient torque applied to certain bolts. That out-of-spec assembly could lead to issues ranging from slight noises to a loss of vehicle control.
The problem was first noticed in December of last year by a GM test fleet driver and eventually tracked back to the improperly torqued bolts on the suspension cradle assembled through July 2012 by a supplier located not too far from the Malibu's Detroit/Hamtramck Assembly Plant. Since an official NHTSA recall notice has not been issued yet, it isn't clear whether or not Detroit-built Malibus were the only ones affected (the 2013 Malibu is also built at GM's Fairfax Assembly Plant in Kansas City, Kansas). Dealers will fix the problem by inspecting vehicles for proper torque specs, retightening if not within specs and, in some cases, perform a rear-wheel alignment.