2012 Subaru Legacy Problems

What owners report

Owners of the 2012 Legacy most often describe the car shuddering, bogging down or shutting off as it comes to a stop, a symptom many attribute to the CVT torque converter. The same low-speed stalling theme shows up across several components, and most reports arrive well past 80,000 miles. Airbag non-deployment in crashes and a recurring warning-light pattern are also reported, but far less often.

1. 1
   Transmission and drivetrain

   Shudder and stall when slowing to a stop (CVT torque

   • 38 complaints (42%)
   • median 105,500 mi at 7.4 yrs old (30 state mileage)
   • filed 2012–2025

   Owners describe the car shuddering, vibrating or cutting out as they brake or slow toward a stop, sometimes in traffic, at lights or when turning at low speed. Some say the engine dies and has to be shifted into park and restarted, and that the behaviour becomes more frequent over time. Dealers reportedly diagnosed a faulty torque converter and recommended replacement, with several owners noting repair estimates in the low thousands of dollars and some mentioning coverage limited to 100,000 miles. Most reports cluster between roughly 75,000 and 170,000 miles, usually during braking or low-speed manoeuvres.

   What to check: Drive the car and brake firmly from around 40 mph and again when rolling slowly, watching for shudder or a drop in revs. Ask whether the torque converter or CVT has been replaced and whether any goodwill coverage applies.

   2 excerpts from owner complaints in NHTSA records

   “I bought this care a few years ago and from day one if ever in traffic or on highway and have to stop really quickly, it will cause the car to stall,, I had no idea what was wrong I loved the car and just avoided stoping abruptly , but as I have learned over the years this is impossible, a car must be able to stop, its life or death serious... …”

   NHTSA complaint #11119402, filed 2018-08, 85,000 miles

   “My Subaru Legacy has been recently stalling when coming to a stop. It shudders and if you do not give it gas or place in neutral, the engine will die. I have read that this is caused from a faulty torque converter that Subaru is aware of but has failed to issue a recall. I'm not sure I would buy another product that isn't fully backed and supported by the manufacturer.”

   NHTSA complaint #10938619, filed 2016-12, 125,208 miles
2. 2
   Air bags

   Airbags not deploying in a collision

   • 5 complaints (6%)
   • median 53,000 mi at 5.4 yrs old (5 state mileage, few)
   • 4 mention a crash, fire or injury
   • filed 2016–2018

   Owners describe collisions at moderate speed, including rear-end and frontal impacts, where the airbags did not deploy and occupants were injured. One complaint describes an airbag warning light staying on with an open circuit diagnosed in the harness and sensor. Several passenger-side inflator recalls cover this model year. Reported at various mileages from about 40,000 to 170,000 miles, always in the context of a crash or warning light.

   Recall 20V001000Recall 20V003000Recall 20V002000Recall 19V008000Recall 19V007000Recall 19V009000Recall 18V012000Recall 17V014000

   What to check: Ask for proof that the passenger-side inflator recalls were completed for this VIN, and confirm the airbag warning light goes out after start-up.

   2 excerpts from owner complaints in NHTSA records

   “On 2/19/14 I was driving s on inter 99 in lindley, ny in r lane when toyota passed me in l lane, lost control, crashed into concrete barrier on l and slid across l and r lanes causing me to crash into his passenger side. My air bag did not deploy and I was injured including permanently to hand. Front end damage $15,345. ## VIN passed ## Subaru Legacy 2012 ##”

   NHTSA complaint #10824298, filed 2016-02, 42,000 miles

   “I was hit in the rear end of the car and hit the car in front of me, but the airbag did not deploy. I was at a complete stop during rush hour on a highway.”

   NHTSA complaint #11021630, filed 2017-09, 92,000 miles
3. 3
   Engine

   Engine stalls after a hard or abrupt stop

   • 12 complaints (13%)
   • median 102,000 mi at 7.3 yrs old (10 state mileage)
   • filed 2012–2023

   A separate group of owners describes the engine quitting specifically after a hard brake application, sometimes with all dashboard lights illuminating and requiring a restart. Some report dealers could not find a cause, while others were told the throttle body or related parts needed replacement. Several owners mention the stall also cutting power steering assistance. Mostly reported between about 60,000 and 150,000 miles, typically after abrupt braking in traffic.

   What to check: During the test drive, brake hard from moderate speed in a safe spot and check that the engine keeps idling. Ask about any throttle body cleaning or replacement.

   2 excerpts from owner complaints in NHTSA records

   “Purchased brand new Subaru Legacy october 31st of 2011. After only five months and 14,000 miles beginning in march of 2012 I was shocked to discover the following problem(s) with my Legacy: low idling, bogging down, at oil light illuminated, and nearly stalling out. This issue is still continuing to this day, sporadically. I now have 25,500 miles and there is no solution to this problem. …”

   NHTSA complaint #10461249, filed 2012-06, 14,000 miles

   “Contact owns a 2012 Subaru Legacy 2.5. While driving at lower speed and approaching a turning lane at a heavy traffic intersection from the highway during rush hour the vehicle vibrated and shuttered abnormally, then stalled with all early computer warning lights going off before engine cut. Owner able to restart vehicle, but cautiously taken to dealer to diagnose with safety concerns while driving. Dealership mechanic unable to diagnose over three hours later. …”

   NHTSA complaint #10926465, filed 2016-11, 61,200 miles
4. 4
   Engine

   Dashboard warning lights flashing together (engine, brake

   • 7 complaints (8%)
   • median 100,000 mi at 3.5 yrs old (7 state mileage, few)
   • filed 2014–2020

   Complaints describe the check engine light coming on together with the brake, traction, cruise and sometimes AT oil temperature indicators. Owners report the lights cycling on and off intermittently, and some say multiple dealer visits failed to reproduce or identify the cause. A few owners link the pattern to a loose fuel cap or failing sensors, with repairs followed by the problem returning. Reported from about 45,000 to 100,000 miles, often intermittently and without a consistent trigger.

   What to check: Check that no warning lamps are lit at idle or after a test drive, and ask whether the fault codes were read and cleared. A scan-tool history can show how often the lights returned.

   2 excerpts from owner complaints in NHTSA records

   “I have been in touch with Subaru regarding their inability to fix a ongoing issue with the engine, cruise control, brake, etc light flashing. At this point we can not pass inspection, sell the car, or use the car. How can a manufacturer be allowed to sell a vehicle they can not fix.”

   NHTSA complaint #10701305, filed 2015-03, 50,000 miles

   “The check engine light goes on and then causes the brake, traction and cruise lights to flash. The lights will go off after some time, not consistently. No authorized Subaru dealer has been able to identify the cause or even record the event.”

   NHTSA complaint #10593194, filed 2014-05, 45,000 miles
5. 5
   Steering

   Steering binds or becomes hard to turn

   • 8 complaints (9%)
   • median 95,000 mi at 7.0 yrs old (6 state mileage, few)
   • filed 2013–2025

   Owners report the steering wheel seizing or failing to return after a turn, and in other cases power assist dropping away entirely with a whining noise. Complaints describe the car wandering or needing constant correction at highway speed. Several say the dealer test drove the car and reported no fault found. Reported from very low mileage up to roughly 125,000 miles, without a clear pattern.

   What to check: Turn the wheel through full lock at parking speed and listen for whining, then drive at highway speed and check for wander. Ask whether the power steering pump or rack has been serviced.

   2 excerpts from owner complaints in NHTSA records

   “Power steering stopped working. I was in the parking lot at work trying to leave at the end of the day. It drove fine over lunch and then when I started the car at 5pm the steering made a whining noise (typical, from my understanding, of a power steering failure) and was very difficult to turn. The steering wheel also did a harsh vibrating thing a little as I was trying to turn as if it was struggling. I knew something was up, so I put it right back in the parking space so that it could be towed. …”

   NHTSA complaint #11186212, filed 2019-03, 75,000 miles

   “Steering wheel nearly locked - became impossible to turn. Happened while making a very slight right turn at about 5mph from a small side road onto a four lane highway. Was able to continue a very very wide turn to get off the road into a parking lot.”

   NHTSA complaint #11091439, filed 2018-05, 125,009 miles

Buying note. Give a 2012 Legacy a thorough test drive that includes hard braking and slow-speed stops, since stalling and shuddering are the most reported themes, and confirm the airbag inflator recalls were done for the specific VIN. Service records showing transmission or torque converter work are worth asking about before purchase.

Summary written with AI from a sample of 60 NHTSA complaints for this model year (picked at random, with complaints that state a mileage and recent ones taken first), then checked automatically against the source records. Where a problem shows a complaint count, every complaint for this model year was matched with fixed keyword rules (written with AI and tested against the sample), and the mileage, age and repair figures are calculated from those complaints; owners' figures are as stated, not verified. Other counts refer to the sample. The excerpts come from NHTSA's public complaint records and are unverified; capitalisation is normalised, NHTSA staff notes are removed, and shortened text ends with “…”. Something wrong? Request a correction.