Local kernel compromise via probe cleanup use-after-free
Published Sep 17, 2026 · Updated Sep 18, 2026
Use-after-free in the rtlwifi PCI probe path in Linux allows local users to compromise the host kernel after IRQ setup failure. rtl_pci_probe() jumps to fail3 when IRQ registration fails, freeing ieee80211 hardware without undoing rfkill, debug, and mac80211 registrations. A local user can then reach dangling objects through nl80211, network-address changes, or rfkill polling, causing kernel reads, writes, control-flow hijack, or a panic.
Summary
What happened
Use-after-free in the rtlwifi PCI probe path in Linux allows local users to compromise the host kernel after IRQ setup failure. rtl_pci_probe() jumps to fail3 when IRQ registration fails, freeing ieee80211 hardware without undoing rfkill, debug, and mac80211 registrations. A local user can then reach dangling objects through nl80211, network-address changes, or rfkill polling, causing kernel reads, writes, control-flow hijack, or a panic.
The record
- CVE
- CVE-2026-90403
- Published
- Sep 17, 2026
- Updated
- Sep 18, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0c8173385e549f95cd80c3fff5aab87b4f881d8d <1b68b6e529ce75112fab98e89583a76370ca394b
- Affected versionversion=0c8173385e549f95cd80c3fff5aab87b4f881d8d <2634998247d24be34ba16a7666f31815ef1da00b
- Affected versionversion=0c8173385e549f95cd80c3fff5aab87b4f881d8d <3c2999d13eeb222ae56631aeb7ca248090f2b210
- Affected versionversion=0c8173385e549f95cd80c3fff5aab87b4f881d8d <86e6187f8525c8f8219eb49e022eba854cc6ab86
- Affected versionversion=0c8173385e549f95cd80c3fff5aab87b4f881d8d <a89818977338ba71194b1ab1d071f0c0848b1e13
- Affected versionversion=0c8173385e549f95cd80c3fff5aab87b4f881d8d <aef178ffae5420afdbf46f7133ed28bd4248e15c
- Affected versionversion=0c8173385e549f95cd80c3fff5aab87b4f881d8d <b42fcfb097da46f0e86564736ced939e83cb8442
- Affected versionversion=0c8173385e549f95cd80c3fff5aab87b4f881d8d <cfd6824dd1d151ab3abc00117b3774c8056006e0
- Affected versionversion=2.6.38
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started