PatchGap
Chrome · DisplayLocking

CVE-2026-113093

Memory Corruption in DisplayLocking
High chrome Memory Corruption 🔧 Commit mapped

Overview

High
Severity
—
CVSS
No
Exploited ITW
Fixed
Fix Status
ImpactMemory corruption in DisplayLocking
DescriptionMemory corruption in DisplayLocking
ComponentDisplayLocking
Bug ClassMemory Corruption
Tracker567612004
Fix commit2f0c9930c59b (chromium/src) +207/-21
CISA KEVNot listed
CreditedXinyang Ge (Anthropic), assisted by Claude
Disclosed2026-10-20

Files Changed

  • third_party/blink/web_tests/external/wpt/css/css-view-transitions/content-visibility-auto-relock-crash.html
  • third_party/blink/web_tests/external/wpt/layout-instability/sources-pseudo-element.html
  • third_party/blink/renderer/core/display_lock/display_lock_document_state.cc
  • third_party/blink/renderer/core/display_lock/display_lock_context.cc
  • third_party/blink/renderer/core/timing/performance.cc
  • third_party/blink/renderer/core/view_transition/view_transition_style_tracker.cc
  • third_party/blink/web_tests/external/wpt/css/css-view-transitions/content-visibility-auto-ancestor-skipped-after-finish.html

Original Bug Report

The reporter's bug is still restricted on the tracker. Chrome de-restricts security bugs ~30–90 days after the fix ships; a later run will backfill it here.
On This Page