platform/x86: hp-bioscfg: pass validated element count to package parsers
In the Linux kernel, the following vulnerability has been resolved: platform/x86: hp-bioscfg: pass validated element count to package parsers The per-type package parsers are handed the wrong element count. hp_init_bios_package_attribute() validates obj->package.count and then calls one of the five hp_populate_*_package_data() wrappers (string, integer, enumeration, ordered list, password). Each wrapper forwards a count to its hp_populate_*_elements_from_package() parser, but instead of forwarding the validated obj->package.count it derives the count from elements[0]. elements[0] is the NAME field and is always an ACPI_TYPE_STRING, so reading ->package.count from it in fact reads ->string.length through the union acpi_object. The parsers thus bound themselves against the length of the name string rather than against the real number of elements in the package. This is safe today because hp_init_bios_package_attribute() refuses any package that has fewer than the type's element count, so a parser only ever runs on a full package and never reads past it regardless of the bogus bound. An upcoming change relaxes that check to accept shorter packages. Once a parser can receive fewer elements than its per-type count, a bound taken from the name length no longer reflects the array size, and the "elem < count" loop conditions and "elem + n >= count" sub-loop guards read past the end of elements[] - an out-of-bounds heap read. Forward the validated obj->package.count to every *_package
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.12.109, 6.18.50, 6.6.157, 7.2.4
- CVEs
- CVE-2026-81011
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 2 Nov 2026, 21:29 UTC · Revision 1
Source evidence
platform/x86: hp-bioscfg: pass validated element count to package parsers
core-osv · Original sourcePublished 11 Sept 2026, 19:43 UTC
In the Linux kernel, the following vulnerability has been resolved: platform/x86: hp-bioscfg: pass validated element count to package parsers The per-type package parsers are handed the wrong element count. hp_init_bios_package_attribute() validates obj->package.count and then calls one of the five hp_populate_*_package_data() wrappers (string, integer, enumeration, ordered list, password). Each wrapper forwards a count to its hp_populate_*_elements_from_package() parser, but instead of forwarding the validated obj->package.count it derives the count from elements[0]. elements[0] is the NAME field and is always an ACPI_TYPE_STRING, so reading ->package.count from it in fact reads ->string.length through the union acpi_object. The parsers thus bound themselves against the length of the name string rather than against the real number of elements in the package. This is safe today because hp_init_bios_package_attribute() refuses any package that has fewer than the type's element count, so a parser only ever runs on a full package and never reads past it regardless of the bogus bound. An upcoming change relaxes that check to accept shorter packages. Once a parser can receive fewer elements than its per-type count, a bound taken from the name length no longer reflects the array size, and the "elem < count" loop conditions and "elem + n >= count" sub-loop guards read past the end of elements[] - an out-of-bounds heap read. Forward the validated obj->package.count to every *_package
osv:CVE-2026-81011
Kernel
Fixed versions: 6.6.157, 6.12.109, 6.18.50, 7.2.4
Complete source record
{
"id": "c6f72142f05df5decd4892506ec48e08b2d7aa45639a78b9accdff3ec8ea44ad",
"url": "https://osv.dev/vulnerability/CVE-2026-81011",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "platform/x86: hp-bioscfg: pass validated element count to package parsers",
"summary": "In the Linux kernel, the following vulnerability has been resolved: platform/x86: hp-bioscfg: pass validated element count to package parsers The per-type package parsers are handed the wrong element count. hp_init_bios_package_attribute() validates obj->package.count and then calls one of the five hp_populate_*_package_data() wrappers (string, integer, enumeration, ordered list, password). Each wrapper forwards a count to its hp_populate_*_elements_from_package() parser, but instead of forwarding the validated obj->package.count it derives the count from elements[0]. elements[0] is the NAME field and is always an ACPI_TYPE_STRING, so reading ->package.count from it in fact reads ->string.length through the union acpi_object. The parsers thus bound themselves against the length of the name string rather than against the real number of elements in the package. This is safe today because hp_init_bios_package_attribute() refuses any package that has fewer than the type's element count, so a parser only ever runs on a full package and never reads past it regardless of the bogus bound. An upcoming change relaxes that check to accept shorter packages. Once a parser can receive fewer elements than its per-type count, a bound taken from the name length no longer reflects the array size, and the \"elem < count\" loop conditions and \"elem + n >= count\" sub-loop guards read past the end of elements[] - an out-of-bounds heap read. Forward the validated obj->package.count to every *_package",
"evidence": "osv:CVE-2026-81011",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.6.157",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.109",
"evidence": "/affected/1/ranges"
},
{
"value": "6.18.50",
"evidence": "/affected/1/ranges"
},
{
"value": "7.2.4",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "CVE-2026-81011",
"aliases": [
"CVE-2026-81011"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "a34fc329b1895fc8a6eb12099adc47009421ba6a"
},
{
"fixed": "467e53f231f77a1677191b8cdabdaf1448439d55"
},
{
"fixed": "436017808c7cbcdb5e49b2142090d4391e3de9a6"
},
{
"fixed": "a38127df99ae8b1851560b35b837c9952416143a"
},
{
"fixed": "400cbc3ccc88a5ad37cd85056224635ce9eba018"
},
{
"fixed": "e0ddfd77c0c320b7d12b6c9169303b140b798775"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-81011.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.6.0"
},
{
"fixed": "6.6.157"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.109"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.50"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.2.4"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-81011.json"
}
}
],
"modified": "2026-10-28T02:30:23.745390659Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/400cbc3ccc88a5ad37cd85056224635ce9eba018",
"https://git.kernel.org/stable/c/436017808c7cbcdb5e49b2142090d4391e3de9a6",
"https://git.kernel.org/stable/c/467e53f231f77a1677191b8cdabdaf1448439d55",
"https://git.kernel.org/stable/c/a38127df99ae8b1851560b35b837c9952416143a",
"https://git.kernel.org/stable/c/e0ddfd77c0c320b7d12b6c9169303b140b798775",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/81xxx/CVE-2026-81011.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-81011",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/81xxx/CVE-2026-81011.json"
}
},
"related_cves": [
{
"value": "CVE-2026-81011",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 490257,
"published_at": "2026-09-11T19:43:01.422+00:00"
}