Skip to main content
CVE-2026-59618VulnerabilityPublished

In smfc_v4l2_s_selection of smfc-v4l2-ioctls.c, there is a possible way to trigger an out of bounds read from adjacent

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-59618· Medium

Not known to be exploited.

Data as of 10 Nov 2026, 23:03 UTC

Severity
Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
GoogleAndroidAffected
  • =Android kernel
Fixed in–

Description

A vulnerability in the smfc_v4l2_s_selection function of smfc-v4l2-ioctls.c allows an out of bounds read from adjacent shared memory buffers due to an integer overflow. This flaw can lead to local information disclosure without requiring additional execution privileges or user interaction.

References

Community reviews

Loading reviews…