What is the CVSS score of CVE-2026-31601?

CVE-2026-31601 has a CVSS 3.1 base score of 5.5 (Medium). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H. EPSS exploitation probability: 0.0%.

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

Yes, a patch is available for CVE-2026-31601. Update the affected software to the latest version immediately.

Linux Kernel CVE-2026-31601

EUVD-2026-25494 MEDIUM

2026-04-24 Linux

GHSA-v3gv-mm6q-h9jf

Information Disclosure Linux Intel

5.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

5.5 MEDIUM

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

vuln.today AI

4.7 MEDIUM

AC:H reflects the non-default SR-IOV/VFIO configuration and migration-unsupported VF required; PR:L for sysfs write access; no confidentiality or integrity impact.

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

4.0 AV:L/AC:H/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

SUSE

MEDIUM

qualitative

Primary rating from NVD.

CVSS VectorNVD

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Lifecycle Timeline

Analysis Generated

Jul 24, 2026 - 02:56 vuln.today

CVSS changed

Apr 29, 2026 - 20:22 NVD

5.5 (MEDIUM)

Patch released

Apr 29, 2026 - 20:15 nvd

Patch available

Apr 24, 2026 - 16:16 EUVD

EUVD ID Assigned

Apr 24, 2026 - 15:00 euvd

EUVD-2026-25494

CVE Published

Apr 24, 2026 - 14:42 nvd

MEDIUM 5.5

DescriptionCVE.org

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

vfio/xe: Reorganize the init to decouple migration from reset

Attempting to issue reset on VF devices that don't support migration leads to the following:

BUG: unable to handle page fault for address: 00000000000011f8 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: Oops: 0000 [#1] SMP NOPTI CPU: 2 UID: 0 PID: 7443 Comm: xe_sriov_flr Tainted: G S U 7.0.0-rc1-lgci-xe-xe-4588-cec43d5c2696af219-nodebug+ #1 PREEMPT(lazy) Tainted: [S]=CPU_OUT_OF_SPEC, [U]=USER Hardware name: Intel Corporation Alder Lake Client Platform/AlderLake-P DDR4 RVP, BIOS RPLPFWI1.R00.4035.A00.2301200723 01/20/2023 RIP: 0010:xe_sriov_vfio_wait_flr_done+0xc/0x80 [xe] Code: ff c3 cc cc cc cc 0f 1f 84 00 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 55 48 89 e5 41 54 53 <83> bf f8 11 00 00 02 75 61 41 89 f4 85 f6 74 52 48 8b 47 08 48 89 RSP: 0018:ffffc9000f7c39b8 EFLAGS: 00010202 RAX: ffffffffa04d8660 RBX: ffff88813e3e4000 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffffc9000f7c39c8 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: ffff888101a48800 R13: ffff88813e3e4150 R14: ffff888130d0d008 R15: ffff88813e3e40d0 FS: 00007877d3d0d940(0000) GS:ffff88890b6d3000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000000011f8 CR3: 000000015a762000 CR4: 0000000000f52ef0 PKRU: 55555554 Call Trace: <TASK> xe_vfio_pci_reset_done+0x49/0x120 [xe_vfio_pci] pci_dev_restore+0x3b/0x80 pci_reset_function+0x109/0x140 reset_store+0x5c/0xb0 dev_attr_store+0x17/0x40 sysfs_kf_write+0x72/0x90 kernfs_fop_write_iter+0x161/0x1f0 vfs_write+0x261/0x440 ksys_write+0x69/0xf0 __x64_sys_write+0x19/0x30 x64_sys_call+0x259/0x26e0 do_syscall_64+0xcb/0x1500 ? __fput+0x1a2/0x2d0 ? fput_close_sync+0x3d/0xa0 ? __x64_sys_close+0x3e/0x90 ? x64_sys_call+0x1b7c/0x26e0 ? do_syscall_64+0x109/0x1500 ? __task_pid_nr_ns+0x68/0x100 ? __do_sys_getpid+0x1d/0x30 ? x64_sys_call+0x10b5/0x26e0 ? do_syscall_64+0x109/0x1500 ? putname+0x41/0x90 ? do_faccessat+0x1e8/0x300 ? __x64_sys_access+0x1c/0x30 ? x64_sys_call+0x1822/0x26e0 ? do_syscall_64+0x109/0x1500 ? tick_program_event+0x43/0xa0 ? hrtimer_interrupt+0x126/0x260 ? irqentry_exit+0xb2/0x710 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7877d5f1c5a4 Code: c7 00 16 00 00 00 b8 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 80 3d a5 ea 0e 00 00 74 13 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 54 c3 0f 1f 00 55 48 89 e5 48 83 ec 20 48 89 RSP: 002b:00007fff48e5f908 EFLAGS: 00000202 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007877d5f1c5a4 RDX: 0000000000000001 RSI: 00007877d621b0c9 RDI: 0000000000000009 RBP: 0000000000000001 R08: 00005fb49113b010 R09: 0000000000000007 R10: 0000000000000000 R11: 0000000000000202 R12: 00007877d621b0c9 R13: 0000000000000009 R14: 00007fff48e5fac0 R15: 00007fff48e5fac0 </TASK>

This is caused by the fact that some of the xe_vfio_pci_core_device members needed for handling reset are only initialized as part of migration init.

Fix the problem by reorganizing the code to decouple VF init from migration init.

AnalysisAI

Kernel panic in the Linux xe/vfio driver causes a denial-of-service when a reset is triggered on SR-IOV Virtual Function (VF) devices that do not support live migration. The xe_vfio_pci_core_device struct members required by reset handling are only initialized during migration setup, leaving them NULL for non-migration VFs; writing to the sysfs reset attribute of such a VF dereferences the uninitialized pointer and crashes the kernel. No public exploit has been identified, EPSS is 0.02% (5th percentile), and exploitation requires a narrow hardware and configuration prerequisite - Intel Xe GPU with SR-IOV and VFIO passthrough enabled.

Technical ContextAI

The vulnerability resides in xe_vfio_pci, the VFIO (Virtual Function I/O) module for Intel's Xe GPU driver in the Linux kernel. SR-IOV VFs can be exposed to guest VMs via VFIO passthrough, and the xe driver supports live migration for some VF types. The bug arises because xe_vfio_pci_core_device struct members consumed by the reset path (xe_sriov_vfio_wait_flr_done and xe_vfio_pci_reset_done) were only allocated and populated during migration init, but reset can be triggered independently via sysfs even when migration was never initialized. The crash at address 0x00000000000011f8 is a classic null-plus-offset dereference - the struct pointer is NULL and the driver accesses a member at offset 0x11f8. CPE cpe:2.3:a:linux:linux identifies the broad kernel codebase; the specific module is xe (drivers/vfio/pci/xe/). No CWE was assigned by NVD, but the root cause maps to CWE-476 (NULL Pointer Dereference) with a secondary initialization-ordering defect.

RemediationAI

The primary fix is to upgrade the Linux kernel to version 7.0.1 or 6.19.14, which contain the upstream stable commits 73e53ff144a538f1843b3dea1e2740a755031cdc and 8fa4113fc65b8b29a30fbbca5fd82221dc6e146e respectively. Ubuntu users should apply the update described in USN-8488-1 (https://ubuntu.com/security/notices/USN-8488-1). Red Hat and SUSE customers should monitor their respective advisories. If patching is not immediately possible, the most effective compensating control is to prevent unprivileged users from writing to the sysfs reset attribute of xe VF devices (e.g., restrict ownership/permissions on /sys/bus/pci/devices/*/reset for VFs managed by xe_vfio_pci), noting this may interfere with legitimate VFIO-based VM management workflows. Alternatively, avoid binding VFs that lack migration support to xe_vfio_pci until patched, though this limits GPU passthrough functionality.

More in Intel

View all

CVE-2021-44228 CRITICAL Act Now POC

10.0 Dec 10

Apache Log4j2 contains a critical JNDI injection vulnerability known as 'Log4Shell' that allows unauthenticated remote c

CVE-2017-5689 CRITICAL Act Now POC

9.8 May 02

An unprivileged network attacker could gain system privileges to provisioned Intel manageability SKUs: Intel Active Mana

CVE-2012-5958 CRITICAL Act Now POC

10.0 Jan 31