Quick answers
- Is CVE-2026-59618 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59618 being exploited in the wild.
- How severe is CVE-2026-59618?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Google Pixel <2026-11-05 patch level.
- Is there a fix for CVE-2026-59618?
- Yes: fixed in Pixel firmware security patch level 2026-11-05 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-59618 attacked?
- It is attacked with local access, in device firmware.
- Am I affected by CVE-2026-59618?
- Check whether you run Google Pixel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Pixel firmware security patch level 2026-11-05 or later
Technical details
An integer overflow in the smfc_v4l2_s_selection function of smfc-v4l2-ioctls.c allows out-of-bounds read access to adjacent shared memory buffers. The vulnerability is triggered locally with no additional execution privileges or user interaction required, and results in information disclosure of data from shared memory regions.
Affected products
- Google Pixel <2026-11-05 patch level
Timeline
- 2026-11-10: disclosed
- 2026-11-05: patched