GHSA-5H39-F843-4G5V
Vulnerability from github – Published: 2026-08-27 06:31 – Updated: 2026-08-27 06:31In the Linux kernel, the following vulnerability has been resolved:
s390/zcrypt: Improve EP11 CPRB length and overflow checks
The xcrb_msg_to_type6_ep11cprb_msgx() function lacks proper input validation, creating security vulnerabilities: 1. Missing minimum size validation: The ep11_cprb structure and subsequent payload fields (pld_tag, pld_lenfmt) are copied from userspace without verifying sufficient buffer length. 2. Arithmetic overflow in length calculations: CEIL4 alignment could overflow, bypassing size checks and enabling buffer overflows. 3. The payload is asn1 encoded but the function just uses a simple c struct overlay to access some fields of the payload.
Fix by using size_t for length calculations, adding U32_MAX boundary checks after alignment, and validating minimum request size and minimum reply size before copying from userspace. Do a very simple asn1 parsing of the payload up to the function value field.
{
"affected": [],
"aliases": [
"CVE-2026-80545"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-26T15:17:08Z",
"severity": "HIGH"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\ns390/zcrypt: Improve EP11 CPRB length and overflow checks\n\nThe xcrb_msg_to_type6_ep11cprb_msgx() function lacks proper input\nvalidation, creating security vulnerabilities:\n1. Missing minimum size validation: The ep11_cprb structure and\n subsequent payload fields (pld_tag, pld_lenfmt) are copied from\n userspace without verifying sufficient buffer length.\n2. Arithmetic overflow in length calculations: CEIL4 alignment could\n overflow, bypassing size checks and enabling buffer overflows.\n3. The payload is asn1 encoded but the function just uses a simple c\n struct overlay to access some fields of the payload.\n\nFix by using size_t for length calculations, adding U32_MAX boundary\nchecks after alignment, and validating minimum request size and\nminimum reply size before copying from userspace. Do a very simple\nasn1 parsing of the payload up to the function value field.",
"id": "GHSA-5h39-f843-4g5v",
"modified": "2026-08-27T06:31:31Z",
"published": "2026-08-27T06:31:31Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-80545"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/17ac0bc866fc624cd05f022dcd8b730c0af11bb1"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/2976b9d2e716c7e5487ca7c29a7bd076cf9adf08"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.