What is CVE-2026-93054?

CVE-2026-93054 is a High severity Linux kernel vulnerability with a CVSS score of 7.0 out of 10, affecting Linux kernel versions from 4.14.100 onward and patched in 5.10.270, 5.15.221, 6.1.188 and others. CVE-2026-93054 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2026-93054?

CVE-2026-93054 has a CVSS score of 7.0 out of 10, rated High severity. The vector string is CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H.

Is there a patch available for CVE-2026-93054?

Yes, CVE-2026-93054 has been patched. Fixed versions include 5.10.270, 5.15.221, 6.1.188 and others. If you are running Linux kernel 4.14.100 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-93054 actively exploited?

CVE-2026-93054 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

CVE-2026-93054

High

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

Package Linux Kernel

Published 2026-09-17

Last modified 2026-09-18

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

7.0

out of 10

High

Attack Vector

Local

Attack Complexity

High

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Vector string

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected versions

Linux kernel versions 4.14.100, 4.18 and later are affected. Fixed in 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6, 7.3-rc1 and their respective stable series.

Affected from

≥ 4.14.100 ≥ 4.18

Fixed in

✓ 5.10.270 5.10.x ✓ 5.15.221 5.15.x ✓ 6.1.188 6.1.x ✓ 6.6.157 6.6.x ✓ 6.12.110 6.12.x ✓ 6.18.52 6.18.x ✓ 7.2.6 7.2.x ✓ 7.3-rc1

References

8 total

Showing 5 of 8 references View all on NVD

Details

CVE ID CVE-2026-93054

Severity High

CVSS score 7.0 / 10

CVSS version 3.1

Published 2026-09-17

Modified 2026-09-18

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-93054?

CVE-2026-93054 is a High severity Linux kernel vulnerability with a CVSS score of 7.0 out of 10 . It affects Linux kernel versions from 4.14.100 onward and has been patched in 5.10.270, 5.15.221, 6.1.188 and others. CVE-2026-93054 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-93054?

CVE-2026-93054 has a CVSS score of 7.0 out of 10, rated High severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H.
Is there a patch available for CVE-2026-93054?

Yes. CVE-2026-93054 has been patched. Fixed versions include 5.10.270, 5.15.221, 6.1.188 and others. If you are running Linux kernel 4.14.100 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-93054 actively exploited?

No. CVE-2026-93054 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.