Google’s Long Term Support channel for ChromeOS just had its busiest month in recent memory. Three weeks after shipping LTS-144’s first security patch, Google pushed a second one on July 28, and the fix list very nearly triples in size. If the July 8 update read like routine maintenance, this one reads like a backlog finally clearing, and it’s a reminder that the same version number can mean very different amounts of catching up depending on which update track a Chromebook is stuck on.
What this patch actually fixes
According to the official Chrome Releases blog, the July 28 build closes five critical use-after-free bugs and 23 high-severity issues, plus one medium-severity flaw in Autofill’s security UI. The five critical fixes land in Input, Network, Ozone, Cast Streaming, and Views, which between them cover keyboard and touchpad handling, the network stack, on-screen rendering, casting video to a TV or Chromecast, and the UI toolkit used to draw menus and windows. The high-severity list is broader still, touching Media, WebXR, PDF rendering, ServiceWorker, Passwords, WebAudio, and WebCodecs. More than half of the 29 fixes, including all five critical ones, share the same underlying flaw type, a use-after-free, where the browser keeps using a piece of memory after it has already been released; that bug class has shown up repeatedly across Chrome and ChromeOS security bulletins all year. As with the July 8 release, Google’s writeup doesn’t flag any of the 29 as under active exploitation.
Why this patch is so much bigger than the last
LTS updates aren’t supposed to be exciting. The entire point of Long Term Support, as we covered when LTS-144’s first patch shipped, is to freeze a Chromebook’s feature set for six months while still delivering security fixes behind the scenes on a rough two-week cadence. Jumping from 10 fixes to 29 in a single cycle says something about how far a frozen branch can drift from an active one. For comparison, Chromebooks on the Stable channel got a genuinely enormous patch of their own in early July, when ChromeOS 149 closed 429 vulnerabilities in a single release. LTS-144 isn’t in that league, but the direction is the same: security work keeps piling up on the Stable channel, and LTS periodically has to absorb a slice of it in one larger-than-usual dose. Stable channel Chromebooks had already moved on to ChromeOS 150 by the time this LTS build shipped, and ChromeOS 151 is now testing in Beta. Google has said some critical fixes can take up to nine months to reach LTS after they’ve already landed everywhere else, and a patch this size looks like several releases’ worth of backported fixes arriving at once.
What Chromebook owners should do
If you own a personal Chromebook and have never touched the channel settings, this update almost certainly doesn’t apply to your device, and you’ve likely had equivalent protection for weeks through the regular Stable channel. That’s worth confirming rather than assuming: open Settings, then About ChromeOS, and check which channel is listed, a distinction our guide to ChromeOS update channels walks through in more detail. If you administer enrolled devices on LTS or LTC through the Google Admin console, in a school, clinic, or one of the managed fleets ChromeOS has quietly taken over, this isn’t a patch worth leaving for the next maintenance window. Five critical bugs sitting unpatched across a fleet of kiosks or shared devices is exactly the scenario LTS exists to prevent, so push the update now rather than waiting for the next scheduled cycle.
LOG 1 report