CVE-2026-23017: idpf: fix error handling in the init_task on load
In the Linux kernel, the following vulnerability has been resolved:
idpf: fix error handling in the inittask on load
If the inittask 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 inittask where the CREATEVPORT (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-vcevent idpfvceventtask [idpf] [40958.168865] RIP: 0010:idpfvceventtask+0x9b/0x350 [idpf] ... [40958.177932] Call Trace: [40958.178491] <TASK> [40958.179040] processonework+0x226/0x6d0 [40958.179609] workerthread+0x19e/0x340 [40958.180158] ? pfxworkerthread+0x10/0x10 [40958.180702] kthread+0x10f/0x250 [40958.181238] ? pfxkthread+0x10/0x10 [40958.181774] retfromfork+0x251/0x2b0 [40958.182307] ? pfxkthread+0x10/0x10 [40958.182834] retfromforkasm+0x1a/0x30 [40958.183370] </TASK>
Fix the error handling in the inittask to make sure the service and mailbox tasks are disabled if the error happens during load. These are started in idpfvccoreinit(), which spawns the inittask 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 idpfvccoreinit() during a successful reset.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linux-azure-6.17to a version that resolves this vulnerability.Fixed in 6.17.0-1021.21~24.04.1 - Upgrade
Upgrade
ubuntu/linux-azure-fde-6.17to a version that resolves this vulnerability.Fixed in 6.17.0-1018.18~24.04.1 - Upgrade
Upgrade
ubuntu/linux-gcp-6.17to a version that resolves this vulnerability.Fixed in 6.17.0-1021.24~24.04.1 - Upgrade
Upgrade
ubuntu/linux-hwe-6.17to a version that resolves this vulnerability.Fixed in 6.17.0-41.41~24.04.1 - Upgrade
Upgrade
ubuntu/linux-nvidia-6.17to a version that resolves this vulnerability.Fixed in 6.17.0-1031.31 - Upgrade
Upgrade
ubuntu/linux-oem-6.17to a version that resolves this vulnerability.Fixed in 6.17.0-1030.30 - Upgrade
Upgrade
ubuntu/linux-oracle-6.17to a version that resolves this vulnerability.Fixed in 6.17.0-1019.19~24.04.3 - Upgrade
Upgrade
ubuntu/linux-realtime-6.17to a version that resolves this vulnerability.Fixed in 6.17.0-1018.20~24.04.1 - Configuration
Update the idpf init_task error handling so that service and mailbox tasks are disabled when init_task fails during driver load, and PTP callbacks are stopped in all failure cases; they will be restarted by idpf_vc_core_init() after a successful reset.
Linux kernel idpf driver init_task error handling = disable service and mailbox tasks on driver-load failure; stop PTP callbacks
Event History
Frequently Asked Questions
What is the severity of CVE-2026-23017?
CVE-2026-23017 has been classified with a moderate severity rating due to its impact on driver loading processes.
How do I fix CVE-2026-23017?
To fix CVE-2026-23017, ensure that your Linux kernel is updated to the latest stable version where the vulnerability is patched.
Which versions of the Linux kernel are affected by CVE-2026-23017?
CVE-2026-23017 affects various versions of the Linux kernel prior to the patch release that addressed the error handling issue.
What components are impacted by CVE-2026-23017?
CVE-2026-23017 primarily impacts the init_task handling during the load of certain drivers, affecting virtual ports and network devices.
Is CVE-2026-23017 a denial-of-service vulnerability?
While CVE-2026-23017 can lead to failures during the driver load process, it does not directly enable denial-of-service but may disrupt functionality.