GHSA-PVFC-84WR-QWJC
Vulnerability from github – Published: 2026-08-15 06:32 – Updated: 2026-08-17 06:33In the Linux kernel, the following vulnerability has been resolved:
afs: handle CB.InitCallBackState3 requests without a server record
The cache manager callback path now attaches the server record to an incoming call through the rxrpc peer's app data. That association is not guaranteed to exist for every callback request, and most callback handlers already tolerate that case.
Make CB.InitCallBackState3 follow the same pattern by checking whether a server record was attached before using it. If the peer is not mapped to a server record, trace the request and ignore it, matching the existing behaviour for other unmatched callback requests.
This keeps the callback handler consistent with the rest of the cache manager service and avoids depending on peer state that may not be available for a given request.
{
"affected": [],
"aliases": [
"CVE-2026-74425"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-15T06:22:44Z",
"severity": "HIGH"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nafs: handle CB.InitCallBackState3 requests without a server record\n\nThe cache manager callback path now attaches the server record to an\nincoming call through the rxrpc peer\u0027s app data. That association is\nnot guaranteed to exist for every callback request, and most callback\nhandlers already tolerate that case.\n\nMake CB.InitCallBackState3 follow the same pattern by checking whether a\nserver record was attached before using it. If the peer is not mapped\nto a server record, trace the request and ignore it, matching the\nexisting behaviour for other unmatched callback requests.\n\nThis keeps the callback handler consistent with the rest of the cache\nmanager service and avoids depending on peer state that may not be\navailable for a given request.",
"id": "GHSA-pvfc-84wr-qwjc",
"modified": "2026-08-17T06:33:44Z",
"published": "2026-08-15T06:32:33Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-74425"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/0bd5f2786a878148190b4c7c259d01313d5f2357"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/42e3917cdbdc3d35e191c525687a6d5427f237fd"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/cc848a080f7a6848dfeef441722419fdcbfe9b8d"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f3cf725cd284b7912d5522babb44721bf38c8887"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/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.