CVE-2026-93116: platform/x86: asus-wmi: fix resource leaks on probe failure
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: Linux Linux 3308b8c5f5a28403611a2f5a46f06aabe4f0c661, 72d792c8053f238ae541fdaa90e609548509b65f, 8410cd2690d463b60527d00ac8cffea2d5a041f6; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
Low priority for now. Upgrade to Linux Linux 3308b8c5f5a28403611a2f5a46f06aabe4f0c661, 72d792c8053f238ae541fdaa90e609548509b65f, 8410cd2690d463b60527d00ac8cffea2d5a041f6; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 17, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- —
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.0
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.17affected
- 0f0ac158d28ff78e75c334e869b1cb8e69372a1f and later · before 72d792c8053f238ae541fdaa90e609548509b65faffected · git
- 0f0ac158d28ff78e75c334e869b1cb8e69372a1f and later · before 959ed35f8c8f07b8dd43c3f917a43ae2f77e4471affected · git
- 0f0ac158d28ff78e75c334e869b1cb8e69372a1f and later · before 8d5999608da60db45949e5459f74f581cdaacd04affected · git
- 0f0ac158d28ff78e75c334e869b1cb8e69372a1f and later · before 8410cd2690d463b60527d00ac8cffea2d5a041f6affected · git
- 0f0ac158d28ff78e75c334e869b1cb8e69372a1f and later · before 3308b8c5f5a28403611a2f5a46f06aabe4f0c661affected · git
- 0f0ac158d28ff78e75c334e869b1cb8e69372a1f and later · before ef3daa2b84a2b8499ce9e2ce1c865dca36d39f95affected · git
- before 5.17not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:13 | linux | before 6.12.115-2 | 6.12.115-2 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-93114Sep 17, 2026 · platform/surface: acpi-notify: Check ACPI companion before use0Monitor
- ← EarlierCVE-2026-93115Sep 17, 2026 · platform/mellanox: mlxbf-pmc: Check ACPI_COMPANION() against NULL0Monitor
- Later →CVE-2026-93117Sep 17, 2026 · usb: fix UAF when probe runs concurrent to dyn ID removal0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 3308b8c5f5a28403611a2f5a46f06aabe4f0c661 | Vendor (CNA) |
| Linux Linux | 72d792c8053f238ae541fdaa90e609548509b65f | Vendor (CNA) |
| Linux Linux | 8410cd2690d463b60527d00ac8cffea2d5a041f6 | Vendor (CNA) |
| Linux Linux | 8d5999608da60db45949e5459f74f581cdaacd04 | Vendor (CNA) |
| Linux Linux | 959ed35f8c8f07b8dd43c3f917a43ae2f77e4471 | Vendor (CNA) |
| Linux Linux | ef3daa2b84a2b8499ce9e2ce1c865dca36d39f95 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 | 6.6.161.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.115-2 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.2.6-1 · Debian:14 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/72d792c8053f238ae541fdaa90e609548509b65f
- git.kernel.org/stable/c/8410cd2690d463b60527d00ac8cffea2d5a041f6
- git.kernel.org/stable/c/8d5999608da60db45949e5459f74f581cdaacd04
- git.kernel.org/stable/c/959ed35f8c8f07b8dd43c3f917a43ae2f77e4471
- git.kernel.org/stable/c/ef3daa2b84a2b8499ce9e2ce1c865dca36d39f95
Vendor advisories and official records. Exploit/PoC links are deliberately left out.