CVE-2026-81005: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-36x4-6h38-8grw
Share
Published
Advisory Summary

CVE-2026-81005 is a security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-81005 at a Glance

CVE Identifier CVE-2026-81005
GHSA Identifier GHSA-36x4-6h38-8grw
Severity N/A
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-81005

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-81005, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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

NVD — CVE-2026-81005 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-81005
git.kernel.org/stable/c/53af3a8bae... WEB
https://git.kernel.org/stable/c/53af3a8bae0a93c1342e1b5519812203332aca8e
git.kernel.org/stable/c/6d920a75df... WEB
https://git.kernel.org/stable/c/6d920a75df9a83ab096b3cde7a643b656e4fdfeb
git.kernel.org/stable/c/75ecc80ef0... WEB
https://git.kernel.org/stable/c/75ecc80ef0614a9f8441ab476fb748d3e919bea8
git.kernel.org/stable/c/8ada17dd4c... WEB
https://git.kernel.org/stable/c/8ada17dd4c4ffd6b94621e735d77eda196ce118f
git.kernel.org/stable/c/b11a1e545a... WEB
https://git.kernel.org/stable/c/b11a1e545ad7a2f8f9ba7276b4ae9429c3399456
git.kernel.org/stable/c/d377bf743f... WEB
https://git.kernel.org/stable/c/d377bf743f29b41729a084a633874ef9c1a13c6a
git.kernel.org/stable/c/d4be659a3e... WEB
https://git.kernel.org/stable/c/d4be659a3e56f4eb16039ab8a1162efea086a714
git.kernel.org/stable/c/f390b0e781... WEB
https://git.kernel.org/stable/c/f390b0e781ca689515b659f94ef05f01497ed833

Frequently Asked Questions

What is CVE-2026-81005?
CVE-2026-81005 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-81005?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-81005?
CVE-2026-81005 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-81005?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-36x4-6h38-8grw",
  "modified" : "2026-09-14T15:32:23Z",
  "published" : "2026-09-11T21:31:24Z",
  "aliases" : [ "CVE-2026-81005" ],
  "details" : "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->si_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's\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->si_sm, and sets\nsmi_info->si_sm and smi_info->intf to NULL.\n\nHowever, intf->in_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->si_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->in_shutdown on the out_err_started path before invoking the\nlower driver's 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.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-81005"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/53af3a8bae0a93c1342e1b5519812203332aca8e"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/6d920a75df9a83ab096b3cde7a643b656e4fdfeb"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/75ecc80ef0614a9f8441ab476fb748d3e919bea8"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/8ada17dd4c4ffd6b94621e735d77eda196ce118f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b11a1e545ad7a2f8f9ba7276b4ae9429c3399456"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d377bf743f29b41729a084a633874ef9c1a13c6a"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d4be659a3e56f4eb16039ab8a1162efea086a714"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f390b0e781ca689515b659f94ef05f01497ed833"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-11T20:19:09Z"
  }
}