Skip to main content

Linux Kernel CVE-2025-40172

HIGH
2025-11-12 416baaa9-dc9f-4396-8d5f-8c081fb06d67
7.8
CVSS 3.1 · Vendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Share

Severity by source

Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67) PRIMARY
7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
5.5 MEDIUM

Local access to the qaic device needed (AV:L, PR:L, AC:L); described impact is an uninitialized-sgt dereference causing a general protection fault, i.e. kernel DoS (A:H) with no clear confidentiality/integrity impact.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Primary rating from Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67).

CVSS VectorVendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

7
Analysis Updated
Jul 30, 2026 - 08:43 vuln.today
v3 (cvss_changed)
Analysis Updated
Jul 30, 2026 - 08:41 vuln.today
v2 (cvss_changed)
Re-analysis Queued
Jul 30, 2026 - 06:37 vuln.today
cvss_changed
CVSS changed
Jul 30, 2026 - 06:37 NVD
7.8 (HIGH)
Patch released
Mar 28, 2026 - 19:30 nvd
Patch available
Analysis Generated
Mar 28, 2026 - 19:21 vuln.today
CVE Published
Nov 12, 2025 - 11:15 nvd
N/A

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

accel/qaic: Treat remaining == 0 as error in find_and_map_user_pages()

Currently, if find_and_map_user_pages() takes a DMA xfer request from the user with a length field set to 0, or in a rare case, the host receives QAIC_TRANS_DMA_XFER_CONT from the device where resources->xferred_dma_size is equal to the requested transaction size, the function will return 0 before allocating an sgt or setting the fields of the dma_xfer struct. In that case, encode_addr_size_pairs() will try to access the sgt which will lead to a general protection fault.

Return an EINVAL in case the user provides a zero-sized ALP, or the device requests continuation after all of the bytes have been transferred.

AnalysisAI

Memory corruption in the Linux kernel's accel/qaic driver (Qualcomm Cloud AI 100 accelerator) allows a local user to trigger a general protection fault by submitting a DMA transfer request with a zero length, or when the device requests continuation (QAIC_TRANS_DMA_XFER_CONT) after all bytes have already been transferred. In these cases find_and_map_user_pages() returns 0 without allocating the scatter-gather table, and encode_addr_size_pairs() then dereferences the unallocated sgt, faulting the kernel. EPSS is very low (0.03%) and there is no public exploit identified at time of analysis, but distro patches (Ubuntu USN-8125-1/8126-1) are already shipping.

Technical ContextAI

The affected component is the accel/qaic driver, the in-kernel driver for Qualcomm's Cloud AI 100 (QAIC) inference accelerator. The driver maps user-supplied buffers for DMA transfers to the device; find_and_map_user_pages() is responsible for pinning user pages and building a scatter-gather table (sgt) describing them, which encode_addr_size_pairs() later walks to emit address/size descriptor pairs for the hardware. The root cause is a missing input-validation / edge-case check: when the requested transfer length is 0, or when resources->xferred_dma_size already equals the requested size on a QAIC_TRANS_DMA_XFER_CONT continuation, the function short-circuits and returns 0 before allocating the sgt or populating the dma_xfer struct. The consumer does not distinguish this early return from a successful mapping and dereferences the never-initialized sgt pointer, producing a general protection fault (an unchecked-return / use-of-uninitialized-resource class defect; NVD lists CWE as N/A).

Affected ProductsAI

The vulnerability is in the mainline Linux kernel's accel/qaic driver and is fixed across multiple stable branches, as indicated by the four kernel.org stable commit references (11f08c30a3e4, 1ab9733d14cc, 48b1d42286bf, 551f1dfbcb7f). No explicit affected version range or CPE string was provided in the input, so exact vulnerable kernel versions must be confirmed from each stable branch and from distribution advisories. Ubuntu is confirmed affected via USN-8125-1 (https://ubuntu.com/security/notices/USN-8125-1) and USN-8126-1 (https://ubuntu.com/security/notices/USN-8126-1). Only systems that load the qaic driver - i.e., hosts equipped with Qualcomm Cloud AI 100 accelerators - are practically exposed.

RemediationAI

Patch available per vendor advisory: apply the upstream kernel fix that returns -EINVAL when the ALP is zero-sized or when the device requests continuation after all bytes have transferred, delivered via the stable commits (git.kernel.org/stable/c/11f08c30a3e4, /1ab9733d14cc, /48b1d42286bf, /551f1dfbcb7f). On Ubuntu, upgrade the kernel to the fixed package versions listed in USN-8125-1 (https://ubuntu.com/security/notices/USN-8125-1) and USN-8126-1 (https://ubuntu.com/security/notices/USN-8126-1) and reboot; other distributions should pull the corresponding backport. If immediate patching is not possible, the effective compensating control is to restrict access to the qaic accelerator device nodes to trusted operators only (tighten permissions/ownership on the device interface, or unload/blacklist the qaic module on hosts that do not require the Cloud AI 100 accelerator) - the trade-off is that blacklisting the module disables use of the AI accelerator entirely, and tightening device permissions may break unprivileged workloads that legitimately submit inference jobs.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
Container suse/hpc/warewulf4-x86_64/sle-hpc-node:latest Image SLES15-SP6 Image SLES15-SP6-BYOS Image SLES15-SP6-BYOS-Azure Image SLES15-SP6-BYOS-EC2 Image SLES15-SP6-BYOS-GCE Image SLES15-SP6-CHOST-BYOS Image SLES15-SP6-CHOST-BYOS-Aliyun Image SLES15-SP6-CHOST-BYOS-Azure Image SLES15-SP6-CHOST-BYOS-EC2 Image SLES15-SP6-CHOST-BYOS-GCE Image SLES15-SP6-CHOST-BYOS-GDC Image SLES15-SP6-CHOST-BYOS-SAP-CCloud Image SLES15-SP6-EC2 Image SLES15-SP6-EC2-ECS-HVM Image SLES15-SP6-GCE Image SLES15-SP6-HPC-BYOS Image SLES15-SP6-HPC-BYOS-Azure Image SLES15-SP6-HPC-BYOS-EC2 Image SLES15-SP6-HPC-BYOS-GCE Image SLES15-SP6-HPC-EC2 Image SLES15-SP6-HPC-GCE Image SLES15-SP6-Hardened-BYOS Image SLES15-SP6-Hardened-BYOS-Azure Image SLES15-SP6-Hardened-BYOS-EC2 Image SLES15-SP6-Hardened-BYOS-GCE Image SLES15-SP6-SAP Image SLES15-SP6-SAP-Azure Image SLES15-SP6-SAP-EC2 Image SLES15-SP6-SAP-GCE Image SLES15-SP6-SAPCAL Image SLES15-SP6-SAPCAL-Azure Image SLES15-SP6-SAPCAL-EC2 Image SLES15-SP6-SAPCAL-GCE Affected
Container suse/sl-micro/6.0/baremetal-os-container:latest Container suse/sl-micro/6.1/baremetal-os-container:latest Affected
Container suse/sl-micro/6.0/base-os-container:2.1.3-7.95 Container suse/sl-micro/6.1/base-os-container:2.2.1-5.80 Affected
Container suse/sl-micro/6.0/kvm-os-container:2.1.3-6.114 Container suse/sl-micro/6.1/kvm-os-container:2.2.1-5.82 Affected
Container suse/sl-micro/6.0/rt-os-container:2.1.3-7.116 Container suse/sl-micro/6.1/rt-os-container:2.2.1-5.55 Affected

Share

CVE-2025-40172 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy