Chrome 156 patches 353 flaws, mostly memory-safety bugs
Original title: Memory Bugs Account for Most of Chrome’s 353 New Security Fixes
Six critical issues are included; Google does not say any are exploited, and stable builds are 156.0.8078.47/.48.
Google promoted Chrome 156 to stable with fixes for 353 vulnerabilities. Most are memory-safety defects: 163 memory corruption bugs, 125 use-after-free issues and 17 out-of-bounds reads, plus 36 improper input validations. The update covers six critical, 61 high, 197 medium and 89 low issues. Google does not mention in-the-wild exploitation.
Unconfirmed: Google does not say whether any of the 353 flaws are exploited.
- Critical fixes are five memory corruption bugs and one use-after-free.
- Windows and macOS get 156.0.8078.47/.48; Linux gets 156.0.8078.47.
- No bounty for 285 flaws; 266 were found by Google.
- Quyen Son at VinFast received $10,000 for a Site Isolation use-after-free.
- Google disclosed $50,000 paid for 24 flaws, with 44 amounts undisclosed.
Impact: Memory corruption and use-after-free flaws in the browser
| Product | Affected | Fixed in |
|---|---|---|
| Google Chrome | before 156.0.8078.47/.48 on Windows and macOS; before 156.0.8078.47 on Linux | 156.0.8078.47/.48 (Windows, macOS); 156.0.8078.47 (Linux) |
- 1.Update Chrome to 156.0.8078.47/.48 on Windows and macOS, or 156.0.8078.47 on Linux.
From the original article
1 min read at securityweek.com
The update fixes 353 flaws, including 163 memory corruption and 125 use-after-free vulnerabilities. The post Memory Bugs Account for Most of Chrome’s 353 New Security Fixes appeared first on SecurityWeek.
By Ionut Arghire · securityweek.com
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.