LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38679: media: venus: Fix OOB read due to missing payload bound check

In the Linux kernel, the following vulnerability has been resolved: media: venus: Fix OOB read due to missing payload bound check Currently, The event_seq_changed() handler processes a variable number of properties sent by the firmware. The number of properties is indicated by the firmware and used to iterate over the payload. However, the payload size is not being validated against the actual message length. This can lead to out-of-bounds memory access if the firmware provides a property count that exceeds the data available in the payload. Such a condition can result in kernel crashes or potential information leaks if memory beyond the buffer is accessed. Fix this by properly validating the remaining size of the payload before each property access and updating bounds accordingly as properties are parsed. This ensures that property parsing is safely bounded within the received message buffer and protects against malformed or malicious firmware behavior.

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

Security readout for executives and security teams

Plain-English summary

A Linux kernel media driver trusted a firmware-provided property count without confirming that the message contained enough data. A malformed message could make the kernel read beyond its buffer, potentially crashing the system or exposing kernel memory.

Executive priority

Treat as a high-priority kernel maintenance issue on systems using the affected media path, particularly appliances where availability or kernel-memory confidentiality matters. It is less urgent for systems without the driver or relevant hardware. No supplied evidence supports emergency incident response for active exploitation.

Technical view

The Venus media driver's event_seq_changed() handler parsed a variable-length firmware payload without checking the remaining message length before each property access. The upstream fix adds per-property bounds validation and updates the remaining payload size during parsing.

Likely exposure

Exposure requires an affected Linux kernel, relevant Venus media-driver functionality, and a firmware message reaching the vulnerable handler. The CVSS vector indicates local access with low privileges; it does not support unauthenticated remote exploitation. Actual reachability depends on deployed hardware, driver activation, firmware, and vendor kernel backports.

Exploitation context

The supplied record is not in CISA KEV and provides no evidence of active exploitation or a public exploit. Documented outcomes are kernel crashes and potential information disclosure. The source also describes malicious firmware as a possible trigger, but does not establish a demonstrated attack chain.

Researcher notes

CVSS 3.1 is 7.3: AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H. The affected-version data in the bundle is ambiguous and should not be interpreted as simple discrete releases. Validate exposure through branch-specific commits and vendor backport status. No CWE was supplied.

Mitigation direction

  • Apply a vendor or distribution kernel update containing the applicable upstream bounds-check fix.
  • Match the deployed kernel branch against the referenced Linux stable commits.
  • Consult Linux distribution or device-vendor guidance where kernel versions include backported fixes.
  • Prioritize systems where the Venus media driver is present and actively used.

Validation and detection

  • Inventory deployed kernel versions and identify systems containing the Venus media driver.
  • Determine whether the driver is loaded or relevant media hardware is enabled.
  • Verify the running kernel includes the applicable stable fix or vendor backport.
  • Review kernel logs for related media-driver crashes or firmware parsing faults.
Prepared
Confidence
high
Sources
6

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-2025-38679 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.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/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
2ADP providers
9Source 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.3CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H1.85.5Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.3High
CVSS 3.1 vector shape for CVE-2025-38679Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/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.

ADP provider summaries

CVECVE Program Container
siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux09c2845e8fe4fcab942929480203f504a6e0a114, 09c2845e8fe4fcab942929480203f504a6e0a114, 09c2845e8fe4fcab942929480203f504a6e0a114, 09c2845e8fe4fcab942929480203f504a6e0a114, 09c2845e8fe4fcab942929480203f504a6e0a114, 09c2845e8fe4fcab942929480203f504a6e0a114unaffected
LinuxLinux4.13, 0, 6.1.149, 6.6.103, 6.12.43, 6.15.11, 6.16.2, 6.17affected
Weakness

CWE details

No CWE listed

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