...
By James Brizuela
Contributing Writer
0
Share
Newsweek is a Trust Project member
See more of our trusted coverage when you search.Prefer Newsweek on Googleto see more of our trusted coverage when you search.
The Baltimore Ravens are struggling in 2025, and that is even more the case due to star quarterback Lamar Jackson suffering a hamstring injury. The injury led to his leaving Week 4 early, and he missed Week 5 as well. Now, the team has made the final decision on the passer for Week 6.
More news: Raiders’ Pete Carroll Reveals Harsh Brock Bowers News Ahead of Titans Game
Jackson is probably attempting to make it back to the field as soon as possible, but hamstring injuries can be tricky. Depending on the severity of the injury, it can often lead to players missing multiple weeks, sometimes months. For the Ravens' signal caller, he is now set to miss his second consecutive game.
Read More on NFL
Per multiple reports, Jackson has been ruled out already for Week 6, leaving Cooper Rush to start in his place. Rush has struggled mightily.
Rush has three interceptions through games, with all three coming against the Houston Texans. At 1-4, Baltimore cannot handle many more losses if they are to be considered a playoff contender.
...
More news: Bengals’ Ja’Marr Chase Hit With Mysterious Illness, Week 6 in Doubt
The issue is that there is no timeline on when Jackson will be healthy enough to return to the field. Clearly, this hamstring injury he suffered is impacting him in a significant way.
The Ravens have a big decision to make regarding Jackson and whether they deem his injury severe enough to make a move at quarterback. Rush is not the answer to keep things afloat while Lamar heals, and that is a big issue.
Early November marks the NFL trade deadline ending, and the Ravens need to make a move on a quarterback if they want to rebound their season. Otherwise, they may have to consider this season lost if Jackson remains out for multiple weeks.
Head to Newsweek Sports for everything on the Ravens and the NFL.
View 0 Comments
Submit Correction
View Editorial & AI Guidelines