LiveActive security incident?Get immediate response
CVE Record

CVE-2026-43256: media: qcom: camss: vfe: Fix out-of-bounds access in vfe_isr_reg_update()

In the Linux kernel, the following vulnerability has been resolved: media: qcom: camss: vfe: Fix out-of-bounds access in vfe_isr_reg_update() vfe_isr() iterates using MSM_VFE_IMAGE_MASTERS_NUM(7) as the loop bound and passes the index to vfe_isr_reg_update(). However, vfe->line[] array is defined with VFE_LINE_NUM_MAX(4): struct vfe_line line[VFE_LINE_NUM_MAX]; When index is 4, 5, 6, the access to vfe->line[line_id] exceeds the array bounds and resulting in out-of-bounds memory access. Fix this by using separate loops for output lines and write masters.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A flaw in the Linux Qualcomm camera subsystem driver can access memory beyond a fixed-size array. A local, low-privileged attacker who can reach the vulnerable driver path may cause serious confidentiality, integrity, or availability impact. Exposure is concentrated on systems using the relevant Qualcomm camera hardware and driver.

Executive priority

Treat this as a high-priority local kernel issue on relevant Qualcomm-based systems, especially shared devices or endpoints where untrusted users have low-privileged access. Prioritize exposure identification and vendor-supported kernel updates. Broad emergency action is not justified without confirming the affected driver or hardware.

Technical view

The VFE interrupt handler iterates across seven image masters while indexing a four-element vfe->line array. Indices 4 through 6 therefore cause out-of-bounds kernel memory access. The upstream correction separates output-line and write-master loops. CVSS 3.1 is 7.8: local access, low complexity, low privileges, no user interaction, and high potential impact.

Likely exposure

Likely exposure is limited to Linux systems using the Qualcomm CAMSS VFE camera driver on affected kernels. The supplied version data lists several affected releases but includes an ambiguous "0" entry and lacks clear ranges. Distribution-specific exposure cannot be determined reliably from this bundle alone.

Exploitation context

The CVSS vector requires local access and low privileges, limiting remote exposure. Successful abuse could affect all three security properties because the access occurs in kernel memory. The CVE is not in KEV, and the supplied sources provide no evidence of active exploitation or a public exploit.

Researcher notes

The root cause is a loop-bound mismatch between seven image masters and four VFE line entries. The fix strategy is documented, but the supplied version representation is insufficient for dependable branch-range analysis. Review the referenced stable commits and downstream package advisories before declaring a build vulnerable or fixed. No exploitation telemetry or CWE classification is supplied.

Mitigation direction

  • Update to a vendor kernel containing the applicable referenced Linux stable fix.
  • Prioritize systems where the Qualcomm CAMSS VFE driver and relevant camera hardware are present.
  • If updating is delayed, obtain vendor guidance; the source bundle names no supported workaround.
  • Track distribution advisories for precise affected and fixed package versions.

Validation and detection

  • Inventory kernel versions and identify systems using the Qualcomm CAMSS VFE driver.
  • Compare kernel package changelogs against the referenced stable fix commits or vendor advisories.
  • Confirm deployed replacement kernels include the fix for vfe_isr_reg_update().
  • Reassess scanner findings after updating and verify affected camera functionality remains operational.
Prepared
Confidence
medium
Sources
8

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-43256 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

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

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2026-43256Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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
LinuxLinux4edc8eae715cecf5f8bf12a0c77c281f336c37db, 4edc8eae715cecf5f8bf12a0c77c281f336c37db, 4edc8eae715cecf5f8bf12a0c77c281f336c37db, 4edc8eae715cecf5f8bf12a0c77c281f336c37db, 4edc8eae715cecf5f8bf12a0c77c281f336c37db, 4edc8eae715cecf5f8bf12a0c77c281f336c37dbunaffected
LinuxLinux5.18, 0, 6.1.167, 6.6.128, 6.12.75, 6.18.16, 6.19.6, 7.0affected
Weakness

CWE details

No CWE listed

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