FKIE_CVE-2026-81005
Vulnerability from fkie_nvd - Published: 2026-09-11 20:19 - Updated: 2026-09-14 13:18
Severity
Summary
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.
References
Impacted products
| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/char/ipmi/ipmi_msghandler.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "75ecc80ef0614a9f8441ab476fb748d3e919bea8",
"status": "affected",
"version": "2512e40e48d21d8bac09f7e91d2c3ceb2d3b50b2",
"versionType": "git"
},
{
"lessThan": "b11a1e545ad7a2f8f9ba7276b4ae9429c3399456",
"status": "affected",
"version": "2512e40e48d21d8bac09f7e91d2c3ceb2d3b50b2",
"versionType": "git"
},
{
"lessThan": "f390b0e781ca689515b659f94ef05f01497ed833",
"status": "affected",
"version": "2512e40e48d21d8bac09f7e91d2c3ceb2d3b50b2",
"versionType": "git"
},
{
"lessThan": "d377bf743f29b41729a084a633874ef9c1a13c6a",
"status": "affected",
"version": "2512e40e48d21d8bac09f7e91d2c3ceb2d3b50b2",
"versionType": "git"
},
{
"lessThan": "d4be659a3e56f4eb16039ab8a1162efea086a714",
"status": "affected",
"version": "2512e40e48d21d8bac09f7e91d2c3ceb2d3b50b2",
"versionType": "git"
},
{
"lessThan": "53af3a8bae0a93c1342e1b5519812203332aca8e",
"status": "affected",
"version": "2512e40e48d21d8bac09f7e91d2c3ceb2d3b50b2",
"versionType": "git"
},
{
"lessThan": "8ada17dd4c4ffd6b94621e735d77eda196ce118f",
"status": "affected",
"version": "2512e40e48d21d8bac09f7e91d2c3ceb2d3b50b2",
"versionType": "git"
},
{
"lessThan": "6d920a75df9a83ab096b3cde7a643b656e4fdfeb",
"status": "affected",
"version": "2512e40e48d21d8bac09f7e91d2c3ceb2d3b50b2",
"versionType": "git"
},
{
"status": "affected",
"version": "288bd736c8a027040fc261c86a87b65e7bc3f6fa",
"versionType": "git"
},
{
"lessThan": "4.19",
"status": "affected",
"version": "4.18.10",
"versionType": "semver"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/char/ipmi/ipmi_msghandler.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "4.19"
},
{
"lessThan": "4.19",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.10.*",
"status": "unaffected",
"version": "5.10.270",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.15.*",
"status": "unaffected",
"version": "5.15.221",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.1.*",
"status": "unaffected",
"version": "6.1.188",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.157",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.109",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.50",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.2.*",
"status": "unaffected",
"version": "7.2.4",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.3-rc1",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nipmi: si: Fix NULL pointer dereference after failed registration\n\ntry_smi_init() allocates new_smi-\u003esi_sm and later calls\nipmi_register_smi_mod(), which maps to ipmi_add_smi().\n\nDuring ipmi_add_smi(), the upper IPMI message handler obtains the\ninitial BMC device information through __bmc_get_device_id(). This can\nfail if the BMC does not return a successful response to the Get Device\nID command.\n\nWhen the BMC returns a nonzero completion code, the device-id helper\nretries the command and eventually returns -EIO if the device ID still\ncannot be fetched.\n\nOn this failure path, ipmi_add_smi() logs \"Unable to get the device id\"\nand goes to out_err_started, where it invokes the lower driver\u0027s\nshutdown callback. try_smi_init() then logs the returned registration\nfailure:\n\n ipmi_si IPI0001:00: IPMI message handler: Unable to get the device id: -5\n ipmi_si IPI0001:00: Unable to register device: error -5\n\nFor ipmi_si, the shutdown callback is shutdown_smi(), which cleans up\nthe SI state machine data, frees smi_info-\u003esi_sm, and sets\nsmi_info-\u003esi_sm and smi_info-\u003eintf to NULL.\n\nHowever, intf-\u003ein_shutdown is not set on this failed-registration\nrollback path. Therefore, the asynchronous redo_bmc_reg work item can\nstill retry BMC device-id probing after the lower driver has already\ncleared its SI state machine data. In the observed case, that retry path\nreached start_next_msg(), which passed the NULL smi_info-\u003esi_sm pointer\nto the selected KCS state machine handler:\n\nBUG: unable to handle kernel NULL pointer dereference at 0000000000000000\nWorkqueue: events redo_bmc_reg [ipmi_msghandler]\nRIP: start_kcs_transaction+0x2c/0x190 [ipmi_si]\nCall Trace:\n start_next_msg+0x50/0x80 [ipmi_si]\n check_start_timer_thread.part.9+0x3b/0x50 [ipmi_si]\n sender+0x69/0x80 [ipmi_si]\n i_ipmi_request+0x2ac/0x9d0 [ipmi_msghandler]\n __get_device_id.isra.29+0xaa/0x180 [ipmi_msghandler]\n __bmc_get_device_id+0xef/0x950 [ipmi_msghandler]\n redo_bmc_reg+0x52/0x60 [ipmi_msghandler]\n process_one_work+0x1a7/0x360\n\nSet intf-\u003ein_shutdown on the out_err_started path before invoking the\nlower driver\u0027s shutdown callback. This prevents later redo_bmc_reg\nretries from using an interface whose lower driver state has been\ncleaned up, and applies the same shutdown state to other IPMI interfaces\nas well."
}
],
"id": "CVE-2026-81005",
"lastModified": "2026-09-14T13:18:54.883",
"metrics": {},
"published": "2026-09-11T20:19:09.173",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/53af3a8bae0a93c1342e1b5519812203332aca8e"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/6d920a75df9a83ab096b3cde7a643b656e4fdfeb"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/75ecc80ef0614a9f8441ab476fb748d3e919bea8"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/8ada17dd4c4ffd6b94621e735d77eda196ce118f"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/b11a1e545ad7a2f8f9ba7276b4ae9429c3399456"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/d377bf743f29b41729a084a633874ef9c1a13c6a"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/d4be659a3e56f4eb16039ab8a1162efea086a714"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/f390b0e781ca689515b659f94ef05f01497ed833"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.
Loading…