LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23131: platform/x86: hp-bioscfg: Fix kobject warnings for empty attribute names

In the Linux kernel, the following vulnerability has been resolved: platform/x86: hp-bioscfg: Fix kobject warnings for empty attribute names The hp-bioscfg driver attempts to register kobjects with empty names when the HP BIOS returns attributes with empty name strings. This causes multiple kernel warnings: kobject: (00000000135fb5e6): attempted to be registered with empty name! WARNING: CPU: 14 PID: 3336 at lib/kobject.c:219 kobject_add_internal+0x2eb/0x310 Add validation in hp_init_bios_buffer_attribute() to check if the attribute name is empty after parsing it from the WMI buffer. If empty, log a debug message and skip registration of that attribute, allowing the module to continue processing other valid attributes.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel issue in the HP BIOS configuration driver. If an HP BIOS reports an attribute with an empty name, the driver can try to register an invalid kernel object and produce warnings. The sources describe a fix that skips those bad attributes. Business risk appears limited, but exposed HP Linux fleets should patch through normal kernel updates.

Executive priority

Treat this as routine kernel hygiene unless local evidence shows repeated kernel warnings or affected HP management workflows. Patch during normal maintenance, with faster handling for managed HP fleets where BIOS configuration features are operationally important.

Technical view

The hp-bioscfg platform/x86 driver parsed BIOS WMI buffer attributes without rejecting empty attribute names. Empty names caused kobject registration warnings in kobject_add_internal. The fix adds validation in hp_init_bios_buffer_attribute() and skips empty-name attributes while continuing valid processing. No CVSS, CWE, or exploitability details are provided in the bundle.

Likely exposure

Exposure appears limited to Linux systems using HP BIOS configuration support through the hp-bioscfg driver. The affected version data in the bundle is incomplete or ambiguous, so kernel and distribution advisories should be checked for exact package status.

Exploitation context

The provided data says this CVE is not in KEV, and no cited source reports active exploitation. The described condition depends on HP BIOS data returning empty attribute names. The bundle does not establish attacker control, privilege impact, or a practical exploitation path.

Researcher notes

The record documents a defensive validation fix rather than a clearly characterized security impact. Key unknowns are exact affected ranges, attacker influence over BIOS WMI data, and whether warnings have availability implications. Avoid assuming exploitation beyond the provided evidence.

Mitigation direction

  • Apply Linux kernel updates from your distribution or vendor when they include the referenced stable fixes.
  • Prioritize HP Linux systems that use BIOS configuration or WMI management features.
  • If immediate patching is not possible, check vendor guidance for supported workarounds.
  • Track distribution advisories for precise affected package versions and backport status.

Validation and detection

  • Inventory HP Linux systems and record kernel versions and distribution kernel package releases.
  • Check whether installed kernels include one of the referenced stable commits or vendor backports.
  • Review kernel logs for hp-bioscfg or kobject warnings about empty names.
  • After updating, confirm the system boots cleanly and hp-bioscfg warnings no longer appear.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-23131 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
5Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxa34fc329b1895fc8a6eb12099adc47009421ba6a, a34fc329b1895fc8a6eb12099adc47009421ba6a, a34fc329b1895fc8a6eb12099adc47009421ba6a, a34fc329b1895fc8a6eb12099adc47009421ba6aunaffected
LinuxLinux6.6, 0, 6.6.122, 6.12.68, 6.18.8, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.