Answer in brief
CVE-2025-38717 records a High severity (CVSS 7.8) vulnerability in net: kcm: Fix race condition in kcm_unattach(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.17:rc1:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 <c0bffbc92a1ca3960fb9cdb8e9f75a68468eb308 || >=ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 <7275dc3bb8f91b23125ff3f47b6529935cf46152 || >=ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 <798733ee5d5788b12e8a52db1519abc17e826f69 || >=ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 <52565a935213cd6a8662ddb8efe5b4219343a25d | c0bffbc92a1ca3960fb9cdb8e9f75a68468eb308, 7275dc3bb8f91b23125ff3f47b6529935cf46152, 798733ee5d5788b12e8a52db1519abc17e826f69, 52565a935213cd6a8662ddb8efe5b4219343a25d |
| Linux/Linuxgeneric | 4.6 | Not reported |
Published upstream
Sep 4, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: net: kcm: Fix race condition in kcm_unattach() syzbot found a race condition when kcm_unattach(psock) and kcm_release(kcm) are executed at the same time. kcm_unattach() is missing a check of the flag kcm->tx_stopped before calling queue_work(). If the kcm has a reserved psock, kcm_unattach() might get executed between cancel_work_sync() and unreserve_psock() in kcm_release(), requeuing kcm->tx_work right before kcm gets freed in kcm_done(). Remove kcm->tx_stopped and replace it by the less error-prone disable_work_sync().
Quoted source text, attributed separately from HOL analysis.