CVE-2025-68808: media: vidtv: initialize local pointers upon transfer of memory ownership
In the Linux kernel, the following vulnerability has been resolved:
media: vidtv: initialize local pointers upon transfer of memory ownership
vidtv_channel_si_init() creates a temporary list (program, service, event)
and ownership of the memory itself is transferred to the PAT/SDT/EIT
tables through vidtv_psi_pat_program_assign(),
vidtv_psi_sdt_service_assign(), vidtv_psi_eit_event_assign().
The problem here is that the local pointer where the memory ownership
transfer was completed is not initialized to NULL. This causes the
vidtv_psi_pmt_create_sec_for_each_pat_entry() function to fail, and
in the flow that jumps to free_eit, the memory that was freed by
vidtv_psi_*_table_destroy() can be accessed again by
vidtv_psi_*_event_destroy() due to the uninitialized local pointer, so it
is freed once again.
Therefore, to prevent use-after-free and double-free vulnerability,
local pointers must be initialized to NULL when transferring memory
ownership.
Security readout for executives and security teams
Plain-English summary
A Linux media driver error can free the same memory twice after an internal failure, potentially corrupting kernel memory. A local user with limited privileges may be able to trigger serious confidentiality, integrity, or availability impact. The supplied evidence does not establish active exploitation.
Executive priority
Prioritize timely remediation on multi-user, development, shared-compute, and other systems allowing local untrusted access. Treat internet-only exposure as unproven because the vulnerability is rated local. Use normal emergency-kernel testing and rollout controls; escalate where sensitive workloads coexist with lower-trust users.
Technical view
In vidtv_channel_si_init(), ownership of program, service, and event allocations transfers to PAT, SDT, and EIT tables without clearing local pointers. If PMT section creation fails and execution reaches free_eit, table destruction frees those objects before stale local pointers cause another access or free, producing use-after-free and double-free conditions.
Likely exposure
Exposure is limited to affected Linux kernels where the vulnerable vidtv media path is present and reachable. The CVSS vector indicates local access, low complexity, low privileges, and no user interaction. The bundle does not specify kernel configuration, module-loading prerequisites, distribution package mappings, or confirmed vulnerable deployments.
Exploitation context
The CVSS 3.1 score is 7.8, with potential high impact to confidentiality, integrity, and availability. CISA KEV status is false, and the supplied sources contain no evidence of active exploitation or a public exploit. Practical exploitability beyond triggering memory corruption is not established.
Researcher notes
The defect is an ownership-lifecycle failure rather than an independently documented bounds flaw. Stable commits initialize transferred local pointers to NULL, preventing cleanup from reusing freed objects. The source bundle lists multiple stable fixes but provides ambiguous version formatting and no distribution mappings, exploit proof, configuration prerequisites, or root-cause CWE.
Mitigation direction
Install a vendor-supported kernel containing the applicable stable fix or backport.
Match deployed kernels against distribution advisories and the affected-version data before prioritizing rollout.
If immediate patching is unavailable, request product-specific mitigation guidance from the Linux distribution vendor.
Restrict untrusted local access until affected systems are updated.
Validation and detection
Inventory kernel versions across Linux hosts and appliances.
Check vendor advisories for package-specific affected and fixed release mappings.
Verify the installed kernel includes the applicable stable commit or an equivalent backport.
Determine whether the vidtv media functionality is configured, available, or used on each system.
After updating, confirm systems booted into the fixed kernel rather than an older installed image.
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-68808 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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
8Source 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.