CVE-2026-23131
Medium · 5.5CVSS
5.5
EPSS
0.1%
Published
Feb 14, 2026
CISA due date
—
Cloudanix analysis
A driver on certain HP computers could receive bad data from the BIOS and cause the operating system to log warnings or become less stable until the software is updated.
- Exploitation
- Local Privilege
- Attacker needs
- Low Privilege
- Complexity
- Low
- Impact
- Denial Of Service
- Component
- OS kernel
- Class
- Improper Input Validation
- Remediation
- Upgrade
- Effort
- Medium
- Patch risk
- Low
What it actually does
Missing input validation in hp-bioscfg allows WMI buffers containing empty attribute name strings to reach kobject registration, triggering repeated kernel warnings at lib/kobject.c and potentially destabilizing the module or system availability.
Why it matters to the business
On affected HP systems running the listed kernel, administrators may observe kernel warnings or experience availability disruptions when the BIOS exposes malformed attributes, increasing operational overhead until systems are updated.
How an attack unfolds
An attacker with local low-privileged access on a vulnerable HP platform triggers the hp-bioscfg driver during boot or module load; the driver parses an empty name from the WMI buffer and attempts kobject_add_internal, producing warnings that can be leveraged to degrade service.
How to fix it
Upgrade linux-aws-5.4 packages to version 5.4.0-1109.118~18.04.1 or later on Ubuntu Pro 18.04 LTS systems; after reboot verify the module no longer registers empty-named kobjects.
How to confirm the fix worked
Confirm installed kernel version matches or exceeds the fixed release, then load the module while monitoring dmesg for absence of the kobject empty-name warning and successful registration of valid attributes only.
Typical attack path
- Obtain local user access on affected Ubuntu 18.04 AWS instance with HP hardware
- Ensure hp-bioscfg module loads or trigger BIOS attribute enumeration
- Supply or induce WMI buffer with empty attribute names
- Observe kernel warnings and potential module or system impact
How to detect it
Search kernel logs (dmesg, /var/log/kern.log, journalctl) for the exact kobject registration warning and the WARNING line from lib/kobject.c; correlate with hp-bioscfg module load events on HP platforms.
- kobject: (00000000135fb5e6): attempted to be registered with empty name!
- WARNING: CPU:.*PID:.*at lib/kobject.c:219 kobject_add_internal+0x2eb/0x310
- hp_init_bios_buffer_attribute
What your security team should do
- Prioritize patching all linux-aws-5.4 instances to 5.4.0-1109.118~18.04.1 within standard change windows
- Add the kobject empty-name warning string to SIEM rules for proactive detection until patches are complete
- Review HP BIOS configurations on affected hardware to identify systems returning empty attribute names
The record
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.
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| Linux | Kernel | 6.6.0 | 6.6.122 |
| openSUSE:Leap 16.0 | dtb-aarch64 | 0 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-64kb | 0 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-azure | 0 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-default | 0 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-default-base | 0 | 6.12.0-160000.27.1.160000.2.8 |
| openSUSE:Leap 16.0 | kernel-docs | 0 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-kvmsmall | 0 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-obs-build | 0 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-obs-qa | 0 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-rt | 0 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-source | 0 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-syms | 0 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-zfcpdump | 0 | 6.12.0-160000.27.1 |
Related vulnerabilities
- CVE-2026-23226 In the Linux kernel, the following vulnerability has been resolved: ksmbd: add chann_lock… Also affects Kernel
- CVE-2026-23225 In the Linux kernel, the following vulnerability has been resolved: sched/mmcid: Don't… Also affects Kernel
- CVE-2026-23230 In the Linux kernel, the following vulnerability has been resolved: smb: client: split… Also affects Kernel
- CVE-2026-23224 In the Linux kernel, the following vulnerability has been resolved: erofs: fix UAF issue… Also affects Kernel
- CVE-2026-23227 In the Linux kernel, the following vulnerability has been resolved: drm/exynos: vidi: use… Also affects Kernel
- CVE-2026-23223 In the Linux kernel, the following vulnerability has been resolved: xfs: fix UAF in… Also affects Kernel
- CVE-2026-23228 In the Linux kernel, the following vulnerability has been resolved: smb: server: fix leak… Also affects Kernel
- CVE-2026-23229 In the Linux kernel, the following vulnerability has been resolved: crypto: virtio - Add… Also affects Kernel