CVE-2026-81014platform/x86: hp-bioscfg: fix heap OOB read in sk_store() and kek_store()
- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: platform/x86: hp-bioscfg: fix heap OOB read in sk_store() and kek_store() sk_store() and kek_store() strip a trailing newline from the sysfs write before allocating the key buffer: length = count; if (buf[length - 1] == '\n') length--; bioscfg_drv.spm_data.signing_key = kmemdup(buf, length, GFP_KERNEL); but then pass the original "count" (not "length") as the copy size to hp_wmi_perform_query(), which memcpy()s that many bytes out of the "length"-sized allocation, reading one byte past it whenever the write ends in a newline, the normal case for a shell "echo" into sysfs. KASAN confirms this directly: BUG: KASAN: slab-out-of-bounds in hp_wmi_perform_query+0x1e9/0x460 [hp_bioscfg] Read of size 28 at addr ffff88813c8e2b80 by task python3/16022 ... sk_store+0xa7/0x240 [hp_bioscfg] kernfs_fop_write_iter+0x3e1/0x5d0 ... The buggy address is located 0 bytes inside of allocated 27-byte region [ffff88813c8e2b80, ffff88813c8e2b9b) Reproduced identically for kek_store, and at multiple write sizes (28, 57, 201 bytes), each time reading exactly one byte past a kmemdup() allocation one byte smaller than the write. Fix by passing "length" instead of "count" to hp_wmi_perform_query() in both functions.
Timeline
ID reserved
By Linux
- 16 days later
· 16 days later
Published
- 38 days later
· 38 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.17% · top 94% of all CVEs (13 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected b2715aa2e1352c0060b9dcba57a2e465bbfbcd68 – < 81db79fed115640736188e56595b1e9aec317d5b
- affected b2715aa2e1352c0060b9dcba57a2e465bbfbcd68 – < 4c6374dcb270d12907b880cf82a5a5ef21785fc3
- affected b2715aa2e1352c0060b9dcba57a2e465bbfbcd68 – < 7cd8fe01aba303a2382db0966eb6c8ab41d5f3c2
- affected b2715aa2e1352c0060b9dcba57a2e465bbfbcd68 – < 67b60703d7d8af1ca0e49f72e1bdb1ccecd41b5b
- affected b2715aa2e1352c0060b9dcba57a2e465bbfbcd68 – < a7508c7959ff8d037327d377ed21a9c0eabe4674
- affected 6.6
- unaffected < 6.6
- unaffected 6.6.157 – ≤ 6.6.*
- unaffected 6.12.109 – ≤ 6.12.*
- unaffected 6.18.50 – ≤ 6.18.*
- unaffected 7.2.4 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References5
- https://git.kernel.org/stable/c/81db79fed115640736188e56595b1e9aec317d5b (opens in a new tab)
- https://git.kernel.org/stable/c/4c6374dcb270d12907b880cf82a5a5ef21785fc3 (opens in a new tab)
- https://git.kernel.org/stable/c/7cd8fe01aba303a2382db0966eb6c8ab41d5f3c2 (opens in a new tab)
- https://git.kernel.org/stable/c/67b60703d7d8af1ca0e49f72e1bdb1ccecd41b5b (opens in a new tab)
- https://git.kernel.org/stable/c/a7508c7959ff8d037327d377ed21a9c0eabe4674 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-76337 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-81014)Record last updated .