Debian LinuxOperating system · Debian
CVE-2015-1272
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUse-after-free vulnerability in the GPU process implementation in Google Chrome before 44.0.2403.89 allows remote attackers to cause a denial of service or possibly have unspecified other impact by leveraging the continued availability of a GPUChannelHost data structure during Blink shutdown, related to content/browser/gpu/browser_gpu_channel_host_factory.cc and content/renderer/render_thread_impl.cc.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceUse-after-free vulnerability in Google Chrome's GPU process where the GPUChannelHost data structure remains accessible during Blink shutdown, allowing remote attackers to cause denial of service or potentially achieve unspecified code execution via a freed memory reference.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Debian LinuxOperating system
= 8.0
Enterprise Linux Desktop SupplementaryOperating system
= 6.0
Enterprise Linux Server SupplementaryOperating system
= 6.0
Enterprise Linux Server Supplementary EusOperating system
= 6.7z
Enterprise Linux Workstation SupplementaryOperating system
= 6.0
ChromeWeb browser
<= 43.0.2357.134= 13.1= 13.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if Google Chrome is installedRun 'google-chrome --version' or 'chromium-browser --version' in a terminal. If the command is not found, Chrome is not installed.Affected if The command executes and returns a version number, indicating Chrome is present on the system.
-
Determine the installed Chrome versionRun 'google-chrome --version' and note the full version string (for example, 43.0.2357.134).Affected if A version number is returned by the command.
-
Compare the installed version against the vulnerable rangeCompare the obtained version number to the affected range: Google Chrome versions up to and including 43.0.2357.134 are vulnerable. Versions later than 43.0.2357.134 are not.Affected if The installed version is 43.0.2357.134 or any earlier version (for example, 43.0.2357.130, 42.x.x.x).
-
Verify the affected Linux distributions if applicableIf using Debian 8.0, RHEL 6.x, or openSUSE 13.1/13.2, check the Chrome version as above. These specific OS versions bundled the vulnerable Chrome version.Affected if The system runs Debian 8.0, RHEL 6.0/6.7z, or openSUSE 13.1/13.2 AND Chrome version is 43.0.2357.134 or earlier.
The system is affected if Google Chrome (or Chromium) version 43.0.2357.134 or any earlier version is installed, regardless of the operating system, as this version contains the use-after-free flaw in the GPU process.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate Google Chrome to version 44.0.2403.89 or later to patch the use-after-free vulnerability in the GPU process implementation.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1272 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-1272 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data