Skip to main content
VulnerabilityPublished Updated

CVE-2025-38717: Linux kernel · net: kcm: Fix race condition in kcm_unattach()

Source GCVE Database

0
Compare

Not known to be exploited · CVSS 4.7 Medium.

Data as of 19 Nov 2026, 02:26 UTC

CVSS 3.1 base score
4.7Medium
How severe the flaw is on the 0–10 CVSS scale.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

AI-suggested

No explicit patch links or vendor advisory content are provided in the input. Until a fix is applied, avoid concurrent operations that trigger kcm_unattach() and kcm_release() simultaneously. Monitor for official Linux kernel updates addressing this issue.

Description

A race condition vulnerability in the Linux kernel's kcm_unattach() function was identified and fixed. The flaw occurs when kcm_unattach(psock) and kcm_release(kcm) execute concurrently, potentially causing a use-after-free scenario by requeuing work on a kcm object that is about to be freed. The issue stems from a missing check of the kcm->tx_stopped flag before queueing work, which was replaced by a safer disable_work_sync() call.

References

Community reviews

Loading reviews…