CVE-2026-68180
Vulnerability Scoring
Analysis In Progress
CVE-2026-68180 Vulnerability Analysis & Exploit Details
CVE-2026-68180
Attack Complexity Details
-
Attack Complexity:
Attack Complexity Analysis In Progress
-
Attack Vector:
Attack Vector Under Analysis
-
Privileges Required:
None
No authentication is required for exploitation.
-
Scope:
Impact is confined to the initially vulnerable component.
-
User Interaction:
None
No user interaction is necessary for exploitation.
CVE-2026-68180 Details
Status: Received on 10 Aug 2026, 13:20 UTC
Last updated: 🕔 19 Aug 2026, 17:20 UTC
Originally published on: 🕐 10 Aug 2026, 13:20 UTC
Time between publication and last update: 9 days
CVSS Release:
CVE-2026-68180 Vulnerability Summary
CVE-2026-68180: In the Linux kernel, the following vulnerability has been resolved: intel_th: fix MSC output device reference leak intel_th_output_open() looks up the output device with bus_find_device_by_devt(), which returns the device with a reference that must be dropped after use. commit 95fc36a234da ("intel_th: fix device leak on output open()") attempted to drop the reference from intel_th_output_release(). However, a successful open replaces file->f_op with the output driver file operations before returning, so close runs the output driver release callback instead. For MSC outputs, close runs intel_th_msc_release(), which only removes the per-file iterator and does not drop the device reference taken by intel_th_output_open(). Consequently, every successful MSC output open leaks one device reference. Drop the device reference from intel_th_msc_release(), which is the release path actually used for MSC output files. Remove the now-unused intel_th_output_release() callback from intel_th_output_fops.
Assessing the Risk of CVE-2026-68180
Access Complexity Graph
The exploitability of CVE-2026-68180 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).
Exploitability Analysis for CVE-2026-68180
No exploitability data is available for CVE-2026-68180.
Understanding AC and PR
A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.
Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.
Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.
CVSS Score Breakdown Chart
Above is the CVSS Sub-score Breakdown for CVE-2026-68180, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.
CIA Impact Analysis
Below is the Impact Analysis for CVE-2026-68180, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.
-
Confidentiality:
None
CVE-2026-68180 does not compromise confidentiality.
-
Integrity:
None
CVE-2026-68180 does not impact data integrity.
-
Availability:
None
CVE-2026-68180 does not affect system availability.
CVE-2026-68180 References
External References
- https://git.kernel.org/stable/c/12ad4fad748e6e563ff4480f03b89134a41b5c37
- https://git.kernel.org/stable/c/141641a70ed337e54487f766ede745fc2ce44c42
- https://git.kernel.org/stable/c/26e27b8dcef1e4df6f30d8f25b3304a506d482b3
- https://git.kernel.org/stable/c/761b785a0cfbce43761227bc42a7f984f31f8921
- https://git.kernel.org/stable/c/c3a28f9cb82425fe0835048ed3677f321e780691
- https://git.kernel.org/stable/c/caba30eb8bd321c465ecfc7d850ee85f5b353496
- https://git.kernel.org/stable/c/ddcf2064d7ec5a8c9afa7cb74442320e443502bc
- https://git.kernel.org/stable/c/df55842fddbcdb80e6dd16680439c0f780ed592e
CWE Common Weakness Enumeration
Unknown
Protect Your Infrastructure against CVE-2026-68180: Combat Critical CVE Threats
Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.
Other 5 Recently Published CVEs Vulnerabilities
- CVE-2026-85200 – The GEO my WP plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 4.5.5.3 via the gmw_posts_locator_aj...
- CVE-2026-85198 – The MPG – Multiple Page Generator, Bulk Landing Pages & Programmatic SEO plugin for WordPress is vulnerable to generic SQL Injection via URL Path i...
- CVE-2026-78175 – The Tutor LMS – eLearning and online course solution plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and includin...
- CVE-2026-78159 – The The Events Calendar plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 6.17.3 via the parse_arra...
- CVE-2026-78006 – The The Events Calendar plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 6.17.4 via the is_safe_wi...