GHSA-477V-9MHF-XMX8
Vulnerability from github – Published: 2026-09-25 12:31 – Updated: 2026-09-25 15:31In the Linux kernel, the following vulnerability has been resolved:
afs: Clear stale peer app data after address list changes
afs_fs_probe_fileserver() fetches the current endpoint state under server->fs_lock, but leaves old_alist as NULL. Consequently, afs_set_peer_appdata() treats every address list replacement as initial setup and only binds the new peers; it never unbinds peers removed from the old list.
An address refresh can therefore proceed as follows. CPU 0 replaces server S's list and drops Pold without clearing Pold->app_data. The server destroyer then clears only S's current peers and lets S reach its RCU callback. After the callback frees S, CPU 1 handles a callback through an RxRPC connection that still pins Pold, reads Pold->app_data, and calls afs_use_server() on the freed object.
KASAN reported:
BUG: KASAN: slab-use-after-free in afs_find_server+0x3c/0xa0 Read of size 4 at addr ffff8881013e1af0 by task krxrpcio/7001/74 Call Trace: afs_find_server+0x3c/0xa0 afs_rx_new_call+0x15c/0x390 rxrpc_new_incoming_call+0x97c/0x1730 rxrpc_input_packet.constprop.0+0xd03/0xec0 rxrpc_io_thread+0x967/0x1640 Allocated by task 93: afs_lookup_server+0x1a7/0x14c0 afs_alloc_server_list+0x43f/0xb60 afs_create_volume+0x923/0x1490 afs_get_tree+0x1c6/0x10a0 Freed by task 0: kfree+0x131/0x3c0 rcu_core+0x50a/0x1850 Last potentially related work creation: __call_rcu_common.constprop.0+0x71/0xa10 afs_put_server+0x213/0x2b0
Preserve old->addresses for the peer app-data update so that removed peers are cleared before the endpoint state is replaced. Also advance both cursors when the old and new lists share a peer; activating the old/new comparison without this would otherwise loop forever on the shared entry.
{
"affected": [],
"aliases": [
"CVE-2026-97583"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-25T11:17:09Z",
"severity": "HIGH"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nafs: Clear stale peer app data after address list changes\n\nafs_fs_probe_fileserver() fetches the current endpoint state under\nserver-\u003efs_lock, but leaves old_alist as NULL. Consequently,\nafs_set_peer_appdata() treats every address list replacement as initial\nsetup and only binds the new peers; it never unbinds peers removed from\nthe old list.\n\nAn address refresh can therefore proceed as follows. CPU 0 replaces\nserver S\u0027s list and drops Pold without clearing Pold-\u003eapp_data. The\nserver destroyer then clears only S\u0027s current peers and lets S reach its\nRCU callback. After the callback frees S, CPU 1 handles a callback\nthrough an RxRPC connection that still pins Pold, reads Pold-\u003eapp_data,\nand calls afs_use_server() on the freed object.\n\nKASAN reported:\n\n BUG: KASAN: slab-use-after-free in afs_find_server+0x3c/0xa0\n Read of size 4 at addr ffff8881013e1af0 by task krxrpcio/7001/74\n Call Trace:\n afs_find_server+0x3c/0xa0\n afs_rx_new_call+0x15c/0x390\n rxrpc_new_incoming_call+0x97c/0x1730\n rxrpc_input_packet.constprop.0+0xd03/0xec0\n rxrpc_io_thread+0x967/0x1640\n Allocated by task 93:\n afs_lookup_server+0x1a7/0x14c0\n afs_alloc_server_list+0x43f/0xb60\n afs_create_volume+0x923/0x1490\n afs_get_tree+0x1c6/0x10a0\n Freed by task 0:\n kfree+0x131/0x3c0\n rcu_core+0x50a/0x1850\n Last potentially related work creation:\n __call_rcu_common.constprop.0+0x71/0xa10\n afs_put_server+0x213/0x2b0\n\nPreserve old-\u003eaddresses for the peer app-data update so that removed\npeers are cleared before the endpoint state is replaced. Also advance\nboth cursors when the old and new lists share a peer; activating the\nold/new comparison without this would otherwise loop forever on the\nshared entry.",
"id": "GHSA-477v-9mhf-xmx8",
"modified": "2026-09-25T15:31:43Z",
"published": "2026-09-25T12:31:25Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-97583"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/3afb988fd0411707bdafb9b321086fff0da28aae"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/7f7f5589d048821dea316cbac9b37d27eaf7530e"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/ba0623fc19a424f4745394c499f9f28a8d88d397"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/c7f77a11a1e719192c7262aad38a3919aec62c21"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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.
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.