[an error occurred while processing this directive]
lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
[an error occurred while processing this directive]
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2026021411-CVE-2026-23131-6201@gregkh>
Date: Sat, 14 Feb 2026 16:10:23 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2026-23131: platform/x86: hp-bioscfg: Fix kobject warnings for empty attribute names

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

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.

The Linux kernel CVE team has assigned CVE-2026-23131 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 6.6 with commit a34fc329b1895fc8a6eb12099adc47009421ba6a and fixed in 6.6.122 with commit 29917c80aa96a25cbcf5876fd774a1cfd72b01a9
	Issue introduced in 6.6 with commit a34fc329b1895fc8a6eb12099adc47009421ba6a and fixed in 6.12.68 with commit 6476be59b7162b891b7bddbd0c2924d87379ef6c
	Issue introduced in 6.6 with commit a34fc329b1895fc8a6eb12099adc47009421ba6a and fixed in 6.18.8 with commit 800b2767905d6b409b8bbe357121970f0b489a89
	Issue introduced in 6.6 with commit a34fc329b1895fc8a6eb12099adc47009421ba6a and fixed in 6.19 with commit fdee1b09721605f532352628d0a24623e7062efb

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2026-23131
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/platform/x86/hp/hp-bioscfg/bioscfg.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/29917c80aa96a25cbcf5876fd774a1cfd72b01a9
	https://git.kernel.org/stable/c/6476be59b7162b891b7bddbd0c2924d87379ef6c
	https://git.kernel.org/stable/c/800b2767905d6b409b8bbe357121970f0b489a89
	https://git.kernel.org/stable/c/fdee1b09721605f532352628d0a24623e7062efb

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ