Log in Start free

Vulnerability · Published Jan 31, 2026 · Assigned by Linux

CVE-2026-23017idpf: fix error handling in the init_task on load

Medium 5.5

In plain English

A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 10% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)5.5Medium
Exploit odds (30 days)0.2%top 89.8% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: idpf: fix error handling in the init_task on load If the init_task fails during a driver load, we end up without vports and netdevs, effectively failing the entire process. In that state a subsequent reset will result in a crash as the service task attempts to access uninitialized resources. Following trace is from an error in the init_task where the CREATE_VPORT (op 501) is rejected by the FW: [40922.763136] idpf 0000:83:00.0: Device HW Reset initiated [40924.449797] idpf 0000:83:00.0: Transaction failed (op 501) [40958.148190] idpf 0000:83:00.0: HW reset detected [40958.161202] BUG: kernel NULL pointer dereference, address: 00000000000000a8 ... [40958.168094] Workqueue: idpf-0000:83:00.0-vc_event idpf_vc_event_task [idpf] [40958.168865] RIP: 0010:idpf_vc_event_task+0x9b/0x350 [idpf] ... [40958.177932] Call Trace: [40958.178491] <TASK> [40958.179040] process_one_work+0x226/0x6d0 [40958.179609] worker_thread+0x19e/0x340 [40958.180158] ? __pfx_worker_thread+0x10/0x10 [40958.180702] kthread+0x10f/0x250 [40958.181238] ? __pfx_kthread+0x10/0x10 [40958.181774] ret_from_fork+0x251/0x2b0 [40958.182307] ? __pfx_kthread+0x10/0x10 [40958.182834] ret_from_fork_asm+0x1a/0x30 [40958.183370] </TASK> Fix the error handling in the init_task to make sure the service and mailbox tasks are disabled if the error happens during load. These are started in idpf_vc_core_init(), which spawns the init_task and has no way of knowing if it failed. If the error happens on reset, following successful driver load, the tasks can still run, as that will allow the netdevs to attempt recovery through another reset. Stop the PTP callbacks either way as those will be restarted by the call to idpf_vc_core_init() during a successful reset.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:13linux6.12.115-2DEBIAN-CVE-2026-23017
Debian:14linux6.18.8-1DEBIAN-CVE-2026-23017
Ubuntu:24.04:LTSlinuxno fix listedUBUNTU-CVE-2026-23017
Ubuntu:25.10linuxno fix listedUBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-23017
Ubuntu:25.10linux-awsno fix listedUBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-23017
Ubuntu:25.10linux-azureno fix listedUBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-azure-6.176.17.0-1021.21~24.04.1UBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-23017
Ubuntu:25.10linux-azure-fdeno fix listedUBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-azure-fde-6.176.17.0-1018.18~24.04.1UBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-23017
Ubuntu:25.10linux-gcpno fix listedUBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-gcp-6.176.17.0-1021.24~24.04.1UBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-hwe-6.176.17.0-41.41~24.04.1UBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-nvidia-6.176.17.0-1031.31UBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-oem-6.176.17.0-1030.30UBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-23017
Ubuntu:25.10linux-oracleno fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-oracle-6.176.17.0-1019.19~24.04.3UBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-23017
Ubuntu:25.10linux-raspino fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-23017
Ubuntu:25.10linux-realtimeno fix listedUBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-23017
Ubuntu:25.10linux-riscvno fix listedUBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-23017
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-vmwareno fix listedUBUNTU-CVE-2026-23017
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2026-23017

Affected products (as reported)

VendorProductVersions
Linux Linux 0fe45467a1041ea3657a7fa3a791c84c104fbd34 – before f32ae3cfc976074e9c5927893ce49bcf12f537480fe45467a1041ea3657a7fa3a791c84c104fbd34 – before a514c374edcd33581cdcccf8faa7cc606a6003190fe45467a1041ea3657a7fa3a791c84c104fbd34 – before 4d792219fe6f891b5b557a607ac8a0a14eda6e38
Linux Linux 6.7

References