LiveActive security incident?Get immediate response
CVE Record

CVE-2026-46239: media: i2c: ov5647: Fix runtime PM refcount leak in s_ctrl

In the Linux kernel, the following vulnerability has been resolved: media: i2c: ov5647: Fix runtime PM refcount leak in s_ctrl Three control cases (AUTOGAIN, EXPOSURE_AUTO, ANALOGUE_GAIN) directly return without calling pm_runtime_put(), causing runtime PM reference count leaks. Change these cases from 'return' to 'ret = ... break' pattern to ensure pm_runtime_put() is always called before function exit.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects the ov5647 camera sensor driver. Certain camera control changes can leak runtime power-management references, potentially leaving device power state accounting wrong. The sources do not show remote attack, privilege escalation, data theft, or active exploitation.

Executive priority

Handle through normal kernel maintenance, with higher priority for fleets using OV5647 camera hardware. There is no source-backed evidence of active exploitation or broad internet-exposed risk in the provided bundle.

Technical view

In media/i2c/ov5647 s_ctrl handling, AUTOGAIN, EXPOSURE_AUTO, and ANALOGUE_GAIN cases returned before pm_runtime_put(). The fix changes those paths to set ret and break, ensuring pm_runtime_put() runs before exit. Impact is documented as a runtime PM refcount leak.

Likely exposure

Exposure appears limited to Linux kernels in the affected ranges that include and use the ov5647 camera sensor driver. Systems without this driver or hardware path are likely not exposed based on the provided sources.

Exploitation context

CISA KEV status is false. The provided sources do not cite public exploitation, exploit availability, CVSS scoring, or a weaponized path. Treat this as a stability and device power-management vulnerability unless vendor guidance adds stronger impact.

Researcher notes

The record lacks CVSS, CWE, detailed impact analysis, and vendor advisories beyond kernel stable commits. Further analysis should focus on affected branch mapping, whether the driver is reachable in deployed builds, and runtime PM behavior before and after the fix.

Mitigation direction

  • Apply Linux vendor or stable kernel updates containing the referenced fixes.
  • Prioritize systems that enable or use the ov5647 camera sensor driver.
  • If patching is delayed, review vendor guidance for supported workarounds.
  • Remove or disable unused ov5647 support only where operationally safe and supported.

Validation and detection

  • Inventory Linux kernel versions against the affected ranges in the CVE record.
  • Confirm whether ov5647 driver support is built, loaded, or used.
  • Verify kernel source or packages include the referenced stable fixes.
  • Regression test camera controls and runtime power-management behavior after updating.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-46239 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
3Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux4f66f36388d5668c215f107a4e1ce1a707251ff5, 4f66f36388d5668c215f107a4e1ce1a707251ff5unaffected
LinuxLinux7.0, 0, 7.0.9, 7.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.