CVE-2026-81005
ipmi: si: Fix NULL pointer dereference after failed registration
Reported by linux · Published September 11, 2026
In the Linux kernel, the following vulnerability has been resolved: ipmi: si: Fix NULL pointer dereference after failed registration try_smi_init() allocates new_smi->si_sm and later calls ipmi_register_smi_mod(), which maps to ipmi_add_smi(). During ipmi_add_smi(), the upper IPMI message handler obtains the initial BMC device information through __bmc_get_device_id(). This can fail if the BMC does not return a successful response to the Get Device ID command. When the BMC returns a nonzero completion code, the device-id helper retries the command and eventually returns -EIO if the device ID still cannot be fetched. On this failure path, ipmi_add_smi() logs "Unable to get the device id" and goes to out_err_started, where it invokes the lower driver's shutdown callback. try_smi_init() then logs the returned registration failure: ipmi_si IPI0001:00: IPMI message handler: Unable to get the device id: -5 ipmi_si IPI0001:00: Unable to register device: error -5 For ipmi_si, the shutdown callback is shutdown_smi(), which cleans up the SI state machine data, frees smi_info->si_sm, and sets smi_info->si_sm and smi_info->intf to NULL. However, intf->in_shutdown is not set on this failed-registration rollback path. Therefore, the asynchronous redo_bmc_reg work item can still retry BMC device-id probing after the lower driver has already cleared its SI state machine data. In the observed case, that retry path reached start_next_msg(), which passed the NULL smi_info->si_sm pointer to the selected KCS state machine handler: BUG: unable to handle kernel NULL pointer dereference at 0000000000000000 Workqueue: events redo_bmc_reg [ipmi_msghandler] RIP: start_kcs_transaction+0x2c/0x190 [ipmi_si] Call Trace: start_next_msg+0x50/0x80 [ipmi_si] check_start_timer_thread.part.9+0x3b/0x50 [ipmi_si] sender+0x69/0x80 [ipmi_si] i_ipmi_request+0x2ac/0x9d0 [ipmi_msghandler] __get_device_id.isra.29+0xaa/0x180 [ipmi_msghandler] __bmc_get_device_id+0xef/0x950 [ipmi_msghandler] redo_bmc_reg+0x52/0x60 [ipmi_msghandler] process_one_work+0x1a7/0x360 Set intf->in_shutdown on the out_err_started path before invoking the lower driver's shutdown callback. This prevents later redo_bmc_reg retries from using an interface whose lower driver state has been cleaned up, and applies the same shutdown state to other IPMI interfaces as well.
EPSS 0.18% · 7.3th percentile
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| kernel6.18-devel | Amazon Linux | 1:6.18.51-120.162.amzn2023 |
| kernel6.18-tools | Amazon Linux | 1:6.18.51-120.162.amzn2023 |
| kernel-modules-extra-common | Amazon Linux | 1:6.1.188-233.385.amzn2023 |
| kernel-tools-devel | Amazon Linux | 1:6.1.188-233.385.amzn2023 |
| kernel6.12-modules-extra-common | Amazon Linux | 1:6.12.110-135.201.amzn2023 |
| kernel-livepatch-6.18.51-120.162 | Amazon Linux | 1:1.0-0.amzn2023 |
| kernel-headers | Amazon Linux | 1:6.1.188-233.385.amzn2023 |
| kernel6.18 | Amazon Linux | 1:6.18.51-120.162.amzn2023 |
| kernel6.12-devel | Amazon Linux | 1:6.12.110-135.201.amzn2023 |
| kernel | Amazon Linux | 1:6.1.188-233.385.amzn2023 |
| kernel6.12-headers | Amazon Linux | 1:6.12.110-135.201.amzn2023 |
| python3-perf6.12 | Amazon Linux | 1:6.12.110-135.201.amzn2023 |
13 more packages have a fixed version. See every fix in Lookup.
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 2512e40e48d21d8bac09f7e91d2c3ceb2d3b50b2, 2512e40e48d21d8bac09f7e91d2c3ceb2d3b50b2, 2512e40e48d21d8bac09f7e91d2c3ceb2d3b50b2 |
| Linux | Linux | 4.19, 0, 5.10.270 |
| amazon:2023 | kernel6.18-devel | 0 |
| amazon:2023 | kernel6.18-tools | 0 |
| amazon:2023 | kernel-modules-extra-common | 0 |
| amazon:2023 | kernel-tools-devel | 0 |
| amazon:2023 | kernel6.12-modules-extra-common | 0 |
| amazon:2023 | kernel-livepatch-6.18.51-120.162 | 0 |
| amazon:2023 | kernel-headers | 0 |
| amazon:2023 | kernel6.18 | 0 |
| amazon:2023 | kernel6.12-devel | 0 |
| amazon:2023 | kernel | 0 |
| amazon:2023 | kernel6.12-headers | 0 |
| amazon:2023 | python3-perf6.12 | 0 |
| amazon:2023 | kernel-devel | 0 |
| amazon:2023 | perf | 0 |
| amazon:2023 | kernel6.12-tools | 0 |
| amazon:2023 | kernel-livepatch-6.12.110-135.201 | 0 |
| amazon:2023 | kernel6.18-tools-devel | 0 |
| amazon:2023 | microvm-kernel6.18 | 0 |
…and 18 more
Timeline
- Sep 11, 2026 CVE Published
- Sep 12, 2026 EPSS Score (11 in total, the first dated here)
- Sep 12, 2026 Coalition ESS Score
- Oct 19, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-81005
vulnetix vdb fixes CVE-2026-81005
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-81005/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart