CVE-2026-97583

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-25. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.5Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

In 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.

CVSS v3
7.5
EG Score
7.5HIGHhigh confidence
EG Risk
38
EG Risk 38/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
32nd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 25, 2026

Last Modified

September 25, 2026

Advisory Details (4)

Auto-updated Sep 25, 2026
No patch confirmed yet.
generic

afs: Clear stale peer app data after address list changes - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ba0623fc19a424f4745394c499f9f28a8d88d397
generic

afs: Clear stale peer app data after address list changes - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7f7f5589d048821dea316cbac9b37d27eaf7530e
generic

afs: Clear stale peer app data after address list changes - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c7f77a11a1e719192c7262aad38a3919aec62c21
generic

afs: Clear stale peer app data after address list changes - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3afb988fd0411707bdafb9b321086fff0da28aae

Vendor Advisories for CVE-2026-97583(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (180 versions)
  • every version up to 7.2.7-1: fixed in 7.2.7-1
—

Data Freshness Timeline

(refreshed 29× in last 7d / 47× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-05 00:24 UTCEG score recompute
  2. 2026-10-05 00:24 UTCGHSA enrichment
  3. 2026-10-04 23:23 UTCEPSS rescore
  4. 2026-10-04 12:31 UTCGHSA enrichment
  5. 2026-10-04 00:41 UTCEG score recompute
  6. 2026-10-04 00:41 UTCGHSA enrichment
  7. 2026-10-03 14:26 UTCEPSS rescore
  8. 2026-10-03 12:52 UTCGHSA enrichment
  9. 2026-10-03 01:02 UTCEG score recompute
  10. 2026-10-03 01:02 UTCGHSA enrichment
  11. 2026-10-02 17:57 UTCEPSS rescore
  12. 2026-10-02 13:12 UTCGHSA enrichment
  13. 2026-10-02 01:19 UTCEG score recompute
  14. 2026-10-02 01:19 UTCGHSA enrichment
  15. 2026-10-01 19:51 UTCEPSS rescore
  16. 2026-10-01 13:29 UTCGHSA enrichment
  17. 2026-10-01 01:39 UTCEG score recompute
  18. 2026-10-01 01:39 UTCGHSA enrichment
  19. 2026-09-30 15:04 UTCEPSS rescore
  20. 2026-09-30 13:50 UTCGHSA enrichment
  21. 2026-09-30 01:59 UTCEG score recompute
  22. 2026-09-30 01:59 UTCGHSA enrichment
  23. 2026-09-29 14:09 UTCGHSA enrichment
  24. 2026-09-29 02:20 UTCEG score recompute
  25. 2026-09-29 02:20 UTCGHSA enrichment
Show 22 more
  1. 2026-09-28 14:30 UTCEG score recompute
  2. 2026-09-28 14:30 UTCGHSA enrichment
  3. 2026-09-28 13:52 UTCEPSS rescore
  4. 2026-09-28 13:52 UTCEPSS rescore
  5. 2026-09-28 02:40 UTCGHSA enrichment
  6. 2026-09-27 14:49 UTCEG score recompute
  7. 2026-09-27 14:49 UTCGHSA enrichment
  8. 2026-09-27 13:49 UTCEPSS rescore
  9. 2026-09-27 02:59 UTCEG score recompute
  10. 2026-09-27 02:59 UTCGHSA enrichment
  11. 2026-09-26 15:59 UTCEPSS rescore
  12. 2026-09-26 15:08 UTCGHSA enrichment
  13. 2026-09-26 03:18 UTCEG score recompute
  14. 2026-09-26 03:17 UTCGHSA enrichment
  15. 2026-09-25 15:24 UTCEG score recompute
  16. 2026-09-25 15:24 UTCGHSA enrichment
  17. 2026-09-25 14:53 UTCEG score recompute▲ 7.50
  18. 2026-09-25 14:52 UTCGHSA enrichment
  19. 2026-09-25 14:49 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  20. 2026-09-25 11:29 UTCNVD update
  21. 2026-09-25 10:39 UTCEG score recompute
  22. 2026-09-25 10:27 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-97583?
CVE-2026-97583 is a high vulnerability published on September 25, 2026. In the Linux kernel, the following vulnerability has been resolved: afs: Clear stale peer app data after address list changes afsfsprobe_fileserver() fetches the current endpoint state under server->fslock, but leaves oldalist as NULL. Consequently, afssetpeer_appdata() treats every address list…
When was CVE-2026-97583 disclosed?
CVE-2026-97583 was first published on September 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-97583 actively exploited?
CVE-2026-97583 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-97583?
CVE-2026-97583 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-97583?
No fix for CVE-2026-97583 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-97583 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-97583

Explore →

Is Your Infrastructure Affected by CVE-2026-97583?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs