CVE-2026-81012

8.4

Linux · Kernel

A buffer overflow vulnerability exists in the Linux kernel hp-bioscfg driver due to an off-by-one error during string buffer operations, potentially allowing memory corruption.

Executive summary

A critical off-by-one buffer overflow in the Linux kernel hp-bioscfg driver could lead to system instability or arbitrary code execution.

Vulnerability

The vulnerability resides in the hp_get_string_from_buffer function within the hp-bioscfg driver. An incorrect conditional check results in an off-by-one error when writing a NUL terminator to destination buffers, which can be triggered by a local attacker to cause memory corruption.

Business impact

The vulnerability carries a CVSS score of 8.4, reflecting its potential for high impact on confidentiality, integrity, and availability. Successful exploitation could allow a local attacker to crash the system or potentially execute arbitrary code with kernel-level privileges. Such an event would result in significant operational disruption and a total compromise of the affected host.

Remediation

Immediate Action: Update the Linux kernel to version 6.12.109, 6.18.50, 7.2.4, or later versions where the fix has been backported.

Proactive Monitoring: Monitor system logs for kernel panic events or repeated segmentation faults specifically related to the hp-bioscfg module.

Compensating Controls: If patching is not immediately feasible, consider blacklisting the hp-bioscfg kernel module to prevent the vulnerable code from executing.

Exploitation status

Public Exploit Available: Unknown

Analyst recommendation

Given the severity of potential kernel-level memory corruption, organizations should prioritize patching affected Linux distributions as part of their standard update cycle. System administrators should verify kernel versions across their fleet and apply the upstream patches provided by their respective distribution maintainers to eliminate this exposure.

More Linux CVEs all →

History

CVE Brief tracked this CVE 1 day before it had a CVSS score.

  1. Disclosed CVE record published
  2. Collected by CVE Brief No CVSS score yet; tracked as early warning
  3. CVSS score assigned 8.4 (3.1)
  4. Analyst report written
  5. Published in the daily brief high section

Sources