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-93054

uio: Fix stale info pointer in failed registration path

Description

In the Linux kernel, the following vulnerability has been resolved: uio: Fix stale info pointer in failed registration path After device_add(), the UIO device is visible to userspace and /dev/uioX can be opened. If a later setup step fails, __uio_register_device() unwinds the device but leaves idev->info pointing at the caller-owned struct uio_info. That is unsafe when an opener races with the failed registration path. The open file keeps a reference to the uio_device, while the caller sees registration failure and may free its struct uio_info. Later file operations can then follow idev->info and dereference freed memory. Handle post-device_add() failures like unregister: remove UIO attributes while the info pointer is still valid, then clear idev->info under info_lock and wake existing waiters/async users before removing the device and minor. This makes already-open file descriptors observe the same "device gone" state as normal uio_unregister_device().

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 32 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-93054, 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.15% · top 96% of all CVEs (11 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 a93e7b331568227500186a465fee3c2cb5dffd1f – < 63eaa7663335d482a8825c231213e312cacea567
    • affected a93e7b331568227500186a465fee3c2cb5dffd1f – < df4faf65194ec6c315a59be4c6749eaeb3009243
    • affected a93e7b331568227500186a465fee3c2cb5dffd1f – < 506b43dde5f9ac0068b1360e6b5dbee07fda59fb
    • affected a93e7b331568227500186a465fee3c2cb5dffd1f – < 15340b00e665af805523b08515294a1aa1778151
    • affected a93e7b331568227500186a465fee3c2cb5dffd1f – < 234156f6c6d9ec35dc47abbcc3adc3c79fc6a5ac
    • affected a93e7b331568227500186a465fee3c2cb5dffd1f – < 16695e9059d80ea6661e8399064b0c01f641dd8c
    • affected a93e7b331568227500186a465fee3c2cb5dffd1f – < ec5bd6731183eb6f619140c9bef2ee11ed818c20
    • affected a93e7b331568227500186a465fee3c2cb5dffd1f – < 67b6fc084b034a91c3ec7907a3fed89a2450f30b
    • affected 085d735c858934e5d5bfaedb1fc98bd9135e6ff1
    • affected 4.14.100 – < 4.15
  • Linux · Linux

    • affected 4.18
    • unaffected < 4.18
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .