Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-93116platform/x86: asus-wmi: fix resource leaks on probe failure

Description

In the Linux kernel, the following vulnerability has been resolved: platform/x86: asus-wmi: fix resource leaks on probe failure During driver initialization in asus_wmi_add(), various subsystems are registered sequentially. However, the error path labels are out of order relative to the registration sequence. Specifically: 1. If asus_wmi_custom_fan_curve_init() fails, the driver jumps to fail_custom_fan_curve. Because this label is placed below fail_sysfs, it bypasses the cleanup calls for the input device and sysfs groups, which were successfully registered before, leaking those resources. 2. If asus_screenpad_init() fails, the driver jumps to fail_screenpad. Because fail_screenpad is placed below fail_backlight, it bypasses the cleanup calls for backlight and rfkill, leaking those resources. Fix these resource leaks by reordering the error path labels in asus_wmi_add() to match the exact reverse order of the resource allocations.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 43 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-93116, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.0CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.0CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.16% · top 94% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.0.

Affected products

  • Linux · Linux

    • affected 0f0ac158d28ff78e75c334e869b1cb8e69372a1f – < 72d792c8053f238ae541fdaa90e609548509b65f
    • affected 0f0ac158d28ff78e75c334e869b1cb8e69372a1f – < 959ed35f8c8f07b8dd43c3f917a43ae2f77e4471
    • affected 0f0ac158d28ff78e75c334e869b1cb8e69372a1f – < 8d5999608da60db45949e5459f74f581cdaacd04
    • affected 0f0ac158d28ff78e75c334e869b1cb8e69372a1f – < 8410cd2690d463b60527d00ac8cffea2d5a041f6
    • affected 0f0ac158d28ff78e75c334e869b1cb8e69372a1f – < 3308b8c5f5a28403611a2f5a46f06aabe4f0c661
    • affected 0f0ac158d28ff78e75c334e869b1cb8e69372a1f – < ef3daa2b84a2b8499ce9e2ce1c865dca36d39f95
  • Linux · Linux

    • affected 5.17
    • unaffected < 5.17
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.57 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-93116 badge
[![CVE-2026-93116](https://cveledger.app/badge/CVE-2026-93116.svg)](https://cveledger.app/cve/CVE-2026-93116)

Record last updated .