GHSA-WW8V-32XC-J2P4
Vulnerability from github – Published: 2026-09-17 18:32 – Updated: 2026-09-17 18:32In the Linux kernel, the following vulnerability has been resolved:
cxl/features: Reject Set Features output buffer smaller than the header
cxlctl_set_feature() sizes its output buffer from the user's fwctl_rpc.out_len but never checks it is large enough to hold even the fwctl_rpc_cxl_out header. With out_len == 0 , kvzalloc() returns ZERO_SIZE_PTR, which passes the !rpc_out check, the subsequent rpc_out->size = 0 then writes through the poison pointer.
Reject requests whose output buffer can't hold the response header, before allocating. The Set Feature reply carries no payload, so the header is all that is required.
{
"affected": [],
"aliases": [
"CVE-2026-93078"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:18:01Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\ncxl/features: Reject Set Features output buffer smaller than the header\n\ncxlctl_set_feature() sizes its output buffer from the user\u0027s\nfwctl_rpc.out_len but never checks it is large enough to hold even the\nfwctl_rpc_cxl_out header. With out_len == 0 , kvzalloc() returns\nZERO_SIZE_PTR, which passes the !rpc_out check, the subsequent\nrpc_out-\u003esize = 0 then writes through the poison pointer.\n\nReject requests whose output buffer can\u0027t hold the response header,\nbefore allocating. The Set Feature reply carries no payload, so the\nheader is all that is required.",
"id": "GHSA-ww8v-32xc-j2p4",
"modified": "2026-09-17T18:32:09Z",
"published": "2026-09-17T18:32:09Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-93078"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/1281dc84c81577b51e2b61c24617c9f44b2cdb99"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/16b7c99eff030c6ea11ca24efa4b9f989cc74093"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/cde18d6c1d913a67ab0afd3d9475ece4be79da50"
}
],
"schema_version": "1.4.0",
"severity": []
}
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.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.