CVE-2026-90324

ublk: check import_ubuf() return value

Published Sep 17, 2026 CVSS 3.1 · 7.8 High EPSS < 1% KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

ublk: check import_ubuf() return value

import_ubuf() can fail if the address range (provided by the userspace
ublk server) is outside the allowed user address space. Return that 0
bytes were copied if import_ubuf() fails rather than passing an
uninitialized struct iov_iter to ublk_copy_user_pages().

Analysis

AI-generated

Technical impact

In the Linux kernel, the ublk subsystem has a flaw where the import_ubuf() function can fail if the user‑space address range provided by the ublk server is outside the allowed user address space. The fault path returns 0 bytes copied on failure but still passes an uninitialized iov_iter struct to ublk_copy_user_pages(), resulting in undefined behavior. This can cause the kernel to copy garbage data or crash, leading to memory corruption, unintended data disclosure, or denial of service.

Affected Systems

All Linux kernels with enabled ublk support are potentially affected. No specific release is enumerated, so any kernel that compiles with ublk should be considered vulnerable until the patch is applied.

Risk and Exploitability

The CVSS score is 7.8, reflecting a moderate to high severity. The EPSS score is below 1%, indicating a low exploitation probability. It is not listed in CISA’s KEV catalog. The vulnerability is likely exploitable by a local user who has access to the ublk driver, such as someone who can control the ublk server process or send crafted requests to the ublk device. The attack would require local privileges but could lead to kernel memory corruption and system compromise if successful.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the Linux kernel to the latest release that includes the CVE‑2026‑90324 fix.
  • If a kernel upgrade cannot be performed immediately, disable or remove the ublk driver from the system configuration to eliminate the vulnerable code path.
  • If the ublk driver must remain in use, restrict its device node permissions so that only trusted local users can access it, and consider placing the ublk server process in a confined environment such as a container or a least‑privilege sandbox.

Generated by OpenCVE AI on September 19, 2026 at 15:39 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4904-1 linux-6.12 security update
Ubuntu USN Ubuntu USN USN-9019-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9020-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9091-1 Linux kernel (NVIDIA Tegra) vulnerabilities
History
Type Values Removed Values Added
Weaknesses CWE-665
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: ublk: check import_ubuf() return value import_ubuf() can fail if the address range (provided by the userspace ublk server) is outside the allowed user address space. Return that 0 bytes were copied if import_ubuf() fails rather than passing an uninitialized struct iov_iter to ublk_copy_user_pages().
Title ublk: check import_ubuf() return value
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 21, 2026, 12:50 PM
Reserved
Sep 11, 2026, 7:38 PM
Status
Received
Published
Sep 17, 2026, 5:17 PM
Modified
Oct 21, 2026, 1:20 PM