Linux
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_data() wrapper so the parsers bound themselves against the real package size. This does not change behaviour for the packages that enumerate correctly today and is a prerequisite for accepting shorter packages safely.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= a34fc329b1895fc8a6eb12099adc47009421ba6a, < 467e53f231f77a1677191b8cdabdaf1448439d55
- >= a34fc329b1895fc8a6eb12099adc47009421ba6a, < 436017808c7cbcdb5e49b2142090d4391e3de9a6
- >= a34fc329b1895fc8a6eb12099adc47009421ba6a, < a38127df99ae8b1851560b35b837c9952416143a
- >= a34fc329b1895fc8a6eb12099adc47009421ba6a, < 400cbc3ccc88a5ad37cd85056224635ce9eba018
- >= a34fc329b1895fc8a6eb12099adc47009421ba6a, < e0ddfd77c0c320b7d12b6c9169303b140b798775
Fixed in 467e53f231f77a1677191b8cdabdaf1448439d55, 436017808c7cbcdb5e49b2142090d4391e3de9a6, a38127df99ae8b1851560b35b837c9952416143a, 400cbc3ccc88a5ad37cd85056224635ce9eba018, e0ddfd77c0c320b7d12b6c9169303b140b798775
- 6.6
Fixed in 0, 6.6.157, 6.12.109, 6.18.50, 7.2.4, 7.3
Mitigation
Upgrade Linux to 467e53f231f77a1677191b8cdabdaf1448439d55 or 436017808c7cbcdb5e49b2142090d4391e3de9a6 or a38127df99ae8b1851560b35b837c9952416143a or 400cbc3ccc88a5ad37cd85056224635ce9eba018 or e0ddfd77c0c320b7d12b6c9169303b140b798775 or later.
Upgrade Linux to 0 or 6.6.157 or 6.12.109 or 6.18.50 or 7.2.4 or 7.3 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.