linux-cve-announce - CVE-2026-23062: platform/x86: hp-bioscfg: Fix kernel panic in GET_INSTANCE

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

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2026020415-CVE-2026-23062-991d@gregkh>
Date: Wed,  4 Feb 2026 17:14:21 +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-23062: platform/x86: hp-bioscfg: Fix kernel panic in GET_INSTANCE_ID macro

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

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

In the Linux kernel, the following vulnerability has been resolved:

platform/x86: hp-bioscfg: Fix kernel panic in GET_INSTANCE_ID macro

The GET_INSTANCE_ID macro that caused a kernel panic when accessing sysfs
attributes:

1. Off-by-one error: The loop condition used '<=' instead of '<',
   causing access beyond array bounds. Since array indices are 0-based
   and go from 0 to instances_count-1, the loop should use '<'.

2. Missing NULL check: The code dereferenced attr_name_kobj->name
   without checking if attr_name_kobj was NULL, causing a null pointer
   dereference in min_length_show() and other attribute show functions.

The panic occurred when fwupd tried to read BIOS configuration attributes:

  Oops: general protection fault [#1] SMP KASAN NOPTI
  KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]
  RIP: 0010:min_length_show+0xcf/0x1d0 [hp_bioscfg]

Add a NULL check for attr_name_kobj before dereferencing and corrects
the loop boundary to match the pattern used elsewhere in the driver.

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


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

	Issue introduced in 6.6 with commit 5f94f181ca25d8c5b77beb2da0cb466ddb6ece29 and fixed in 6.6.122 with commit eb5ff1025c92117d5d1cc728bcfa294abe484da1
	Issue introduced in 6.6 with commit 5f94f181ca25d8c5b77beb2da0cb466ddb6ece29 and fixed in 6.12.68 with commit eba49c1dee9c5e514ca18e52c545bba524e8a045
	Issue introduced in 6.6 with commit 5f94f181ca25d8c5b77beb2da0cb466ddb6ece29 and fixed in 6.18.8 with commit 193922a23d7294085a47d7719fdb7d66ad0a236f
	Issue introduced in 6.6 with commit 5f94f181ca25d8c5b77beb2da0cb466ddb6ece29 and fixed in 6.19-rc7 with commit 25150715e0b049b99df664daf05dab12f41c3e13

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-23062
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.h


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/eb5ff1025c92117d5d1cc728bcfa294abe484da1
	https://git.kernel.org/stable/c/eba49c1dee9c5e514ca18e52c545bba524e8a045
	https://git.kernel.org/stable/c/193922a23d7294085a47d7719fdb7d66ad0a236f
	https://git.kernel.org/stable/c/25150715e0b049b99df664daf05dab12f41c3e13