Kernel memory compromise via raced UIO teardown
Published Sep 17, 2026 · Updated Sep 18, 2026
Use-after-free in affected Linux UIO core releases allows local users to read or modify kernel memory through a raced device open. After device_add() exposes /dev/uioX, __uio_register_device() can fail without clearing idev->info, so later file operations dereference a caller-freed uio_info structure. A low-privileged account must access the UIO node and win a high-complexity race during a later setup failure; successful abuse can crash the kernel or compromise kernel memory.
Summary
What happened
Use-after-free in affected Linux UIO core releases allows local users to read or modify kernel memory through a raced device open. After device_add() exposes /dev/uioX, __uio_register_device() can fail without clearing idev->info, so later file operations dereference a caller-freed uio_info structure. A low-privileged account must access the UIO node and win a high-complexity race during a later setup failure; successful abuse can crash the kernel or compromise kernel memory.
The record
- CVE
- CVE-2026-93054
- 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=085d735c858934e5d5bfaedb1fc98bd9135e6ff1
- Affected versionversion=4.14.100 <4.15
- Affected versionversion=4.18
- Affected versionversion=a93e7b331568227500186a465fee3c2cb5dffd1f <15340b00e665af805523b08515294a1aa1778151
- Affected versionversion=a93e7b331568227500186a465fee3c2cb5dffd1f <16695e9059d80ea6661e8399064b0c01f641dd8c
- Affected versionversion=a93e7b331568227500186a465fee3c2cb5dffd1f <234156f6c6d9ec35dc47abbcc3adc3c79fc6a5ac
- Affected versionversion=a93e7b331568227500186a465fee3c2cb5dffd1f <506b43dde5f9ac0068b1360e6b5dbee07fda59fb
- Affected versionversion=a93e7b331568227500186a465fee3c2cb5dffd1f <63eaa7663335d482a8825c231213e312cacea567
- Affected versionversion=a93e7b331568227500186a465fee3c2cb5dffd1f <67b6fc084b034a91c3ec7907a3fed89a2450f30b
- Affected versionversion=a93e7b331568227500186a465fee3c2cb5dffd1f <df4faf65194ec6c315a59be4c6749eaeb3009243
- Affected versionversion=a93e7b331568227500186a465fee3c2cb5dffd1f <ec5bd6731183eb6f619140c9bef2ee11ed818c20
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