⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● High · CVSS 8.8

How to Fix CVE-2026-6315: Use-after-free in Chrome

By Sai Kiran Pandrala. Last verified: 2026-05-25.

⚡ At a glance
Severity8.8 (High)
Actively exploited?No public listing in CISA KEV
AffectedGoogle Chrome 147.0.7727.101 to <147.0.7727.101
Fixed inChrome 147.0.7727.101
Type (CWE)CWE-416: Use after free

What is CVE-2026-6315?

Use after free in Permissions in Google Chrome on Android prior to 147.0.7727.101 allowed a remote attacker who convinced a user to engage in specific UI gestures to execute arbitrary code via a crafted HTML page. (Chromium security severity: High)

Am I affected?

Run the version check that matches your platform:


# Android: Settings -> About phone -> Android version / Security patch level

Compare what you see against the Affected row above (Google Chrome 147.0.7727.101 to <147.0.7727.101). If your build sits inside that range, you are exposed and should patch.

How to fix CVE-2026-6315

The primary fix is to upgrade Chrome to the patched build. Use the commands for your platform below; the patched version listed in the vendor advisory is: Chrome 147.0.7727.101.

Android

Open Settings -> System -> System update -> Check for update on the device, then install the security patch issued by the vendor (OEM or Google). On supported Pixel devices:


# Vendor advisory: https://chromereleases.googleblog.com/2026/04/stable-channel-update-for-desktop_15.html
# From a workstation with adb + the OTA package
adb sideload <android-patched-ota>.zip

If you can't patch immediately

If you cannot apply the patched version today, restrict exposure with one of the following runnable controls. None replace the patch.

Service-level fallback


# If the affected feature is optional, stop the service until the patch is applied
sudo systemctl stop chrome
sudo systemctl disable chrome

How to verify the fix worked


# Linux
chrome --version 2>/dev/null || dpkg -s chrome | grep -i version
rpm -q chrome 2>/dev/null || true


# Windows
winget list | findstr /I "chrome"
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above Chrome 147.0.7727.101. Restart any services that loaded the old library (systemctl restart <service> on Linux, restart the Windows service or reboot when prompted). For network appliances, run show version on the device and confirm the build matches the patched release.

Frequently asked questions

Other vulnerabilities in the same area that are worth patching alongside this one:

Is CVE-2026-6315 actually being exploited?

According to the data sources above, no public confirmation of in-the-wild exploitation at this time. Either way, the fix is the same: apply the vendor patch.

Do I need to reboot after patching?

For OS or kernel updates, yes. For most userland packages a systemctl restart <service> is enough. Any process that loaded the old shared library keeps using it until restarted, so when in doubt, reboot.

What is the CVSS score?

8.8 (high). Refer to the vendor advisory for the exact vector string.

Where is the official advisory?

See the References section at the bottom of this page; the vendor's URL is the authoritative source for affected builds and patched versions.

References

*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*