GHSA-954M-592C-4VPC
Vulnerability from github – Published: 2026-07-19 18:31 – Updated: 2026-08-11 18:30In the Linux kernel, the following vulnerability has been resolved:
fwctl: pds: Validate RPC input size before parsing
The fwctl core allocates the device-specific RPC input buffer with fwctl_rpc.in_len and passes that buffer to the driver callback.
pdsfc_fw_rpc() casts the buffer to struct fwctl_rpc_pds and then calls pdsfc_validate_rpc(), which reads fields from that structure before checking that the input buffer is large enough to contain it. A short in_len can make pds_fwctl read beyond the allocation.
Reject pds RPC buffers that are smaller than struct fwctl_rpc_pds before parsing any pds-specific fields.
{
"affected": [],
"aliases": [
"CVE-2026-64101"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-07-19T16:17:51Z",
"severity": "MODERATE"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nfwctl: pds: Validate RPC input size before parsing\n\nThe fwctl core allocates the device-specific RPC input buffer with\nfwctl_rpc.in_len and passes that buffer to the driver callback.\n\npdsfc_fw_rpc() casts the buffer to struct fwctl_rpc_pds and then calls\npdsfc_validate_rpc(), which reads fields from that structure before\nchecking that the input buffer is large enough to contain it. A short\nin_len can make pds_fwctl read beyond the allocation.\n\nReject pds RPC buffers that are smaller than struct fwctl_rpc_pds before\nparsing any pds-specific fields.",
"id": "GHSA-954m-592c-4vpc",
"modified": "2026-08-11T18:30:37Z",
"published": "2026-07-19T18:31:52Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-64101"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/0d470d36551058e3f728574308b815a80bca710f"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/9e3f18883a98420a3b8873c6f894bc57e9b98e41"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/e7537735028c3ad4b0bfc02ff8fa2a1a28aa04fe"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.
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.