Ashwin Tears Into CSK Over Mhatre's Hamstring — 'You Made Him Run Another Ball'

It was the fifth over at the Rajiv Gandhi International Stadium. CSK were chasing 195. Ayush Mhatre — 18 years old, the franchise's leading run-scorer in IPL 2026, the one Chennai's struggling top order had been leaning on — had just raced to 30 off 12 balls and was turning for a second run.

He never made it. Mhatre pulled up halfway down the pitch, clutching his hamstring, flinging off his helmet. Tommy Simsek, CSK's physio, jogged out. There was a long conference. A decision was made. And this is where R Ashwin says Chennai got it wrong — twice.

Mhatre stayed on. The next ball, bowled by Nitish Kumar Reddy, was nudged to leg. Gaikwad called his visibly hobbling partner for a single. Mhatre limped through it. The ball after that, he flayed wildly at extra cover — a shot with no footwork, no balance, no hope — and Heinrich Klaasen held a screamer. CSK's best batter of the season walked off unable to walk, assisted by Ramakrishna Ghosh and the physio. The scans came back. Hamstring tear.

Ashwin, who spent two stints at CSK and knows the dressing room better than most current pundits, wasn't pulling punches. His criticism came in two parts, and the first one cuts deeper than the second.

Part one: Mhatre shouldn't have been playing in the first place. "While coming into bat, Mhatre came with a strap on his knee. For two-three matches now, he had been playing as the impact sub, and his injury had been a concern." In other words — CSK knew he was carrying something. They played him anyway. They asked a teenage body to absorb the load of their entire top order while one of its joints was strapped up.

Part two: Once the hamstring went, the response was indefensible. Instead of retiring hurt — which is what any sensible medical protocol would have dictated — Mhatre stayed at the crease. A hamstring tear, Ashwin implied, is the kind of injury that gets worse the longer you load it. The call Gaikwad took for a single on the very next ball wasn't malicious. But it was the difference between a grade-one strain and a grade-two tear. Between two weeks out and, potentially, six months.

Mike Hussey, CSK's batting coach, didn't try to sugarcoat it at the post-match press conference. "It looks pretty bad. He will undergo scans," Hussey said. "He's going to be a big loss because he has been in nice touch."

"Nice touch" is English understatement for the only CSK batter consistently performing this season. Mhatre's 201 runs at a strike rate of 177.87 are, in context, more valuable than Gaikwad's scores, more sustainable than Sanju Samson's cameos, and — here's the painful part — more important than anything Dhoni has done, because Dhoni is still recovering from a calf injury of his own and hasn't played a match all season.

CSK's injury list now reads like a medical bulletin: Dhoni (calf), Mhatre (hamstring tear), Khaleel Ahmed (ruled out), Nathan Ellis (ruled out). And the team sitting tenth in the points table, looking for answers. The 18-year-old who was providing those answers just got carried off the field by a physio and a teammate.

Here's the uncomfortable truth at the heart of this. Mhatre's injury wasn't caused by Gaikwad. The hamstring went on a second run that Mhatre himself initiated. But what happened after the injury — the decision to keep him out there, to take a single on the next ball, to put a teenager with a torn hamstring through another moment of sprinting — that's a failure of on-field leadership.

Gaikwad is CSK's captain. He's also the man who called the single that forced Mhatre to limp through another run. Former India bowler S. Sreesanth has been scathing all season about Gaikwad's captaincy instincts, and on social media, the response to this moment has been even less generous. "I wish Mhatre had opened" was trending before the injury. After it, the mood shifted from frustration to genuine anger — a captain who can't read a teammate's pain level, fans argued, shouldn't be reading field placements.

Ashwin, to his credit, didn't pile onto the captain. His criticism was broader — "the team" — which in CSK speak means captain, coach, physio, and the Dhoni-era hierarchy that still hovers over every decision. But the moment that gets replayed, the one that hurts to watch, is Gaikwad's wave for the single. Twenty-six seconds that may have cost Chennai their best batter until August.

Ashwin's most pointed observation — the one that got buried under the retire-hurt debate — was about how CSK had been using Mhatre in the weeks leading up to the injury. "For two-three matches now, he had been playing as the impact sub, and his injury had been a concern."

Impact Sub, in the modern IPL, is supposed to be a tactical lever — a specialist you deploy for a specific phase. CSK had been using it as a way to hide Mhatre's knee strap, bringing him on to bat when his fielding workload could be skipped. That works for one match. It doesn't work as a season-long strategy, because a body that's only loaded when batting is a body that never gets truly match-conditioned. The hamstring, Ashwin implied, was waiting to go.

And it finally did — on a second run, on a night when CSK needed their 18-year-old prodigy to deliver another 50, not another injury. The scans will determine how long Mhatre is out. But the broader question Ashwin is asking — why was he even out there with a strap on, and why was he asked to take another run after the tear — is one CSK's management will need to answer publicly. Because fans are asking it already. Loudly.