Skip to content
Noroxi
CVE-2026-93054· NVD / CVE Program· CNA Linux

uio: Fix stale info pointer in failed registration path

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.14% (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 15340b00e665af805523b08515294a1aa1778151, 16695e9059d80ea6661e8399064b0c01f641dd8c, 234156f6c6d9ec35dc47abbcc3adc3c79fc6a5ac; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.

Low priority for now. Upgrade to Linux Linux 15340b00e665af805523b08515294a1aa1778151, 16695e9059d80ea6661e8399064b0c01f641dd8c, 234156f6c6d9ec35dc47abbcc3adc3c79fc6a5ac; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 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: 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().

HighCVSS 7.0 · v3.1—No exploit Fix available
Published
Sep 17, 2026
Updated
Oct 19, 2026
EPSS
0.1% · 3th percentile
CWE
—

Report tools

JSON

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.

Follow CVE-2026-93054

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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

    • 085d735c858934e5d5bfaedb1fc98bd9135e6ff1, 4.18affected
    • a93e7b331568227500186a465fee3c2cb5dffd1f and later · before 63eaa7663335d482a8825c231213e312cacea567affected · git
    • a93e7b331568227500186a465fee3c2cb5dffd1f and later · before df4faf65194ec6c315a59be4c6749eaeb3009243affected · git
    • a93e7b331568227500186a465fee3c2cb5dffd1f and later · before 506b43dde5f9ac0068b1360e6b5dbee07fda59fbaffected · git
    • a93e7b331568227500186a465fee3c2cb5dffd1f and later · before 15340b00e665af805523b08515294a1aa1778151affected · git
    • a93e7b331568227500186a465fee3c2cb5dffd1f and later · before 234156f6c6d9ec35dc47abbcc3adc3c79fc6a5acaffected · git
    • a93e7b331568227500186a465fee3c2cb5dffd1f and later · before 16695e9059d80ea6661e8399064b0c01f641dd8caffected · git
    • a93e7b331568227500186a465fee3c2cb5dffd1f and later · before ec5bd6731183eb6f619140c9bef2ee11ed818c20affected · git
    • a93e7b331568227500186a465fee3c2cb5dffd1f and later · before 67b6fc084b034a91c3ec7907a3fed89a2450f30baffected · git
    • 4.14.100 and later · before 4.15affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.190-16.1.190-1
Debian:12linux-6.12before 6.12.111-1~deb12u16.12.111-1~deb12u1
Debian:13linuxbefore 6.12.111-16.12.111-1
Debian:14linuxbefore 7.2.6-17.2.6-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-93052Sep 17, 2026 · misc: bcm-vk: Use acquire/release for msgq_inited
    0Monitor
  • ← EarlierCVE-2026-93053Sep 17, 2026 · speakup: keyhelp: guard letter_offsets possible out-of-range indexing
    0Monitor
  • Later →CVE-2026-93055Sep 17, 2026 · UDF symlink pathComponent header OOB read
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux15340b00e665af805523b08515294a1aa1778151Vendor (CNA)
Linux Linux16695e9059d80ea6661e8399064b0c01f641dd8cVendor (CNA)
Linux Linux234156f6c6d9ec35dc47abbcc3adc3c79fc6a5acVendor (CNA)
Linux Linux4.15Vendor (CNA)
Linux Linux506b43dde5f9ac0068b1360e6b5dbee07fda59fbVendor (CNA)
Linux Linux63eaa7663335d482a8825c231213e312cacea567Vendor (CNA)
Linux Linux67b6fc084b034a91c3ec7907a3fed89a2450f30bVendor (CNA)
Linux Linuxdf4faf65194ec6c315a59be4c6749eaeb3009243Vendor (CNA)
Linux Linuxec5bd6731183eb6f619140c9bef2ee11ed818c20Vendor (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.06.6.157.1-1 · Release NotesMicrosoft (MSRC)
debian:linux6.1.190-1 · Debian:12Package registry (OSV)
debian:linux6.12.111-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.111-1~deb12u1 · Debian:12Package 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.

EPSS, last 120 days

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 researchers

Finders, 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

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records