{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80543 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80543 is a vulnerability in Linux, published on 26 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-80543 and fix it if it is affected.\n\nWhat it is: CVE-2026-80543 is a vulnerability in Linux, published on 26 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-80543 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-80543/ (Markdown: https://insights.sbomify.com/CVE-2026-80543/index.md)","id":"CVE-2026-80543","markdown":"https://insights.sbomify.com/CVE-2026-80543/index.md","name":"CVE-2026-80543","record":{"aliases":["DEBIAN-CVE-2026-80543","GHSA-r429-pxmh-55v9","UBUNTU-CVE-2026-80543"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"Local attackers can read uninitialized kernel memory via s390 crypto driver due to missing padding, potentially exposing sensitive data to firmware.","user_interaction":"not_required","vuln_class":"information_disclosure"},"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\ns390/zcrypt: Pad trailing CCA or EP11 message with zeros\n\nThe both functions xcrb_msg_to_type6cprb_msgx() and\nxcrb_msg_to_type6_ep11cprb_msgx() copy the user space message into a\nkernel buffer based on the message length. But on further processing\nthe message is supposed to be 4 byte length adjusted. Thus up to 3\nbytes of uninitialized kernel memory are forwarded to further\nprocessing steps and may unwanted expose kernel memory to the crypto\ncard firmware.\n\nThis patch contains code to pad the gap between user space copied\nmessage and message buffer length sent down to further processing of\nthe CCA or EP11 message to zeros.","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":"s390/zcrypt: Pad trailing CCA or EP11 message with zeros","id":"CVE-2026-80543","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"s390/zcrypt: Improve EP11 CPRB domain handling with ASN.1 parsing","id":"CVE-2026-80544"},"packages":[],"prev":{"headline":"drm/amd/display: Fix NULL pointer dereference in amdgpu_dm_crtc_set_vblank()","id":"CVE-2026-80542"},"products":["Linux"],"published":"2026-08-26","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-21","vendors":["Linux"]},"summary":"Local attackers can read uninitialized kernel memory via s390 crypto driver due to missing padding, potentially exposing sensitive data to firmware.","url":"https://insights.sbomify.com/CVE-2026-80543/"}