CVE-2026-93054

CVE CVE-2026-93054EUVD EUVD-2026-82164Published 2026-09-17T16:10:43.000ZLast changed 2026-09-18T17:55:48.000ZCVSS 7.0

What the advisory describes

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().

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux a93e7b331568227500186a465fee3c2cb5dffd1f <506b43dde5f9ac0068b1360e6b5dbee07fda59fb; a93e7b331568227500186a465fee3c2cb5dffd1f <16695e9059d80ea6661e8399064b0c01f641dd8c; a93e7b331568227500186a465fee3c2cb5dffd1f <ec5bd6731183eb6f619140c9bef2ee11ed818c20; patch: 6.6.157; patch: 5.15.221; a93e7b331568227500186a465fee3c2cb5dffd1f <63eaa7663335d482a8825c231213e312cacea567; patch: 5.10.270; a93e7b331568227500186a465fee3c2cb5dffd1f <15340b00e665af805523b08515294a1aa1778151; a93e7b331568227500186a465fee3c2cb5dffd1f <df4faf65194ec6c315a59be4c6749eaeb3009243; 4.14.100 <4.15; 4.18; patch: 6.18.52; a93e7b331568227500186a465fee3c2cb5dffd1f <67b6fc084b034a91c3ec7907a3fed89a2450f30b; patch: 0; 085d735c858934e5d5bfaedb1fc98bd9135e6ff1; patch: 6.12.110; patch: 6.1.188; a93e7b331568227500186a465fee3c2cb5dffd1f <234156f6c6d9ec35dc47abbcc3adc3c79fc6a5ac; patch: 7.2.6; patch: 7.3-rc1

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.