{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-81013 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-81013 is a memory corruption vulnerability in Linux, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-81013 and fix it if it is affected.\n\nWhat it is: CVE-2026-81013 is a memory corruption vulnerability in Linux, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-81013 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-81013/ (Markdown: https://insights.sbomify.com/CVE-2026-81013/index.md)","id":"CVE-2026-81013","markdown":"https://insights.sbomify.com/CVE-2026-81013/index.md","name":"CVE-2026-81013","record":{"aliases":["AZL-100424","BELL-CVE-2026-81013","DEBIAN-CVE-2026-81013","GHSA-66mm-3gmh-q6v8","UBUNTU-CVE-2026-81013"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"low_privilege","summary":"A local attacker can trigger a heap out-of-bounds read in the HP BIOS configuration driver by writing an empty password, potentially leaking adjacent kernel memory.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nplatform/x86: hp-bioscfg: fix heap OOB read on empty password write\n\nvalidate_password_input() computes length = strlen(buf) and then\nchecks buf[length - 1] to strip a trailing newline, without checking\nthat length is nonzero first. Writing an empty string (a bare '\\n')\nto current_password or new_password gives length == 0, and\nbuf[length - 1] reads buf[-1], one byte before the heap allocation\nholding the copied input.\n\nKASAN confirms this directly:\n\n  BUG: KASAN: slab-out-of-bounds in store_password_instance.constprop.0+0x223/0x2a0 [hp_bioscfg]\n  Read of size 1 at addr ffff88811bd8da9f by task sh/13740\n  ...\n  store_password_instance.constprop.0+0x223/0x2a0 [hp_bioscfg]\n  current_password_store+0x14/0x20 [hp_bioscfg]\n  ...\n  The buggy address is located 23 bytes to the right of\n  allocated 8-byte region [ffff88811bd8da80, ffff88811bd8da88)\n\nReproduced identically via new_password_store. Execution continues\npast the bad read (the garbage byte only affects whether \"length\" is\ndecremented by one), so the write completes and returns success; this\nis a pure information read past the buffer, not a crash, but it is\nstill an out-of-bounds access KASAN correctly flags.\n\nFix by only checking buf[length - 1] when length is nonzero.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"platform/x86: hp-bioscfg: fix heap OOB read on empty password write","id":"CVE-2026-81013","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"platform/x86: hp-bioscfg: fix heap OOB read in sk_store() and kek_store()","id":"CVE-2026-81014"},"packages":[],"prev":{"headline":"platform/x86: hp-bioscfg: fix off-by-one write in hp_get_string_from_buffer()","id":"CVE-2026-81012"},"products":["Linux"],"published":"2026-09-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A local attacker can trigger a heap out-of-bounds read in the HP BIOS configuration driver by writing an empty password, potentially leaking adjacent kernel memory.","url":"https://insights.sbomify.com/CVE-2026-81013/"}