{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-99023 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-99023 is a vulnerability in Linux, published on 23 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-99023 and fix it if it is affected.\n\nWhat it is: CVE-2026-99023 is a vulnerability in Linux, published on 23 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-99023 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-99023/ (Markdown: https://insights.sbomify.com/CVE-2026-99023/index.md)","id":"CVE-2026-99023","markdown":"https://insights.sbomify.com/CVE-2026-99023/index.md","name":"CVE-2026-99023","record":{"aliases":["DEBIAN-CVE-2026-99023","GHSA-x8r3-6q3f-q5x9","UBUNTU-CVE-2026-99023"],"analysis":null,"analysis_generated_by":null,"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\npower: sequencing: pcie-m2: Fix leaking array from of_regulator_bulk_get_all()\n\nof_regulator_bulk_get_all() allocates the consumers array and hands it to\nthe caller, who is expected to free it at an appropriate time.\npwrseq-pcie-m2.c never did, leading to a memory leak.\n\nAdd an explicit kfree() for the consumers array.","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":"power: sequencing: pcie-m2: Fix leaking array from of_regulator_bulk_get_all()","id":"CVE-2026-99023","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"optee: register TEE devices only once fully initialized","id":"CVE-2026-99024"},"packages":[],"prev":{"headline":"regulator: ltc3676: don't read the write-only HRST and CLIRQ registers","id":"CVE-2026-99022"},"products":["Linux"],"published":"2026-10-23","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-23","vendors":["Linux"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-99023/"}