{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72156 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72156 is a memory corruption vulnerability in Linux, published on 15 Aug 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-72156 and fix it if it is affected.\n\nWhat it is: CVE-2026-72156 is a memory corruption vulnerability in Linux, published on 15 Aug 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-72156 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-72156/ (Markdown: https://insights.sbomify.com/CVE-2026-72156/index.md)","id":"CVE-2026-72156","markdown":"https://insights.sbomify.com/CVE-2026-72156/index.md","name":"CVE-2026-72156","record":{"aliases":["BELL-CVE-2026-72156","DEBIAN-CVE-2026-72156","GHSA-46j9-hjxg-9ff5","UBUNTU-CVE-2026-72156"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel FPGA driver","requires_auth":"none","summary":"A zero header_size in a Microchip SPI FPGA bitstream causes an out-of-bounds read, potentially leaking memory or crashing the kernel.","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\nfpga: microchip-spi: fix zero header_size OOB read in mpf_ops_parse_header()\n\nmpf_ops_parse_header() reads header_size from the bitstream at\nMPF_HEADER_SIZE_OFFSET (24). When header_size is zero, the expression\n*(buf + header_size - 1) reads one byte before the buffer start.\n\nSince initial_header_size is set to 71 in mpf_ops, the fpga-mgr core\nguarantees the buffer is large enough to reach MPF_HEADER_SIZE_OFFSET.\nThe only real gap is the zero header_size case, which cannot be\nresolved by providing a larger buffer, so return -EINVAL.","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":"fpga: microchip-spi: fix zero header_size OOB read in mpf_ops_parse_header()","id":"CVE-2026-72156","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"net: thunderbolt: Fix frags[] overflow by bounding frame_count","id":"CVE-2026-72157"},"packages":[],"prev":{"headline":"mtd: spi-nor: swp: Improve locking user experience","id":"CVE-2026-72155"},"products":["Linux"],"published":"2026-08-15","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-08-17","vendors":["Linux"]},"summary":"A zero header_size in a Microchip SPI FPGA bitstream causes an out-of-bounds read, potentially leaking memory or crashing the kernel.","url":"https://insights.sbomify.com/CVE-2026-72156/"}