CVE-2025-39830: Linux kernel · Memory Leak
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium · fixed in 86d13a6f49cb68aa91bd718b1b627e72e77285c1 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 11:20 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-01-14.
- Patch
- Available – fixed in 86d13a6f49cb68aa91bd718b1b627e72e77285c1, 4ccdbf50dd88a2a7399409e68887dd8077f6a562, 2c0a959bebdc1ada13cf9a8242f177c5400299e6
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 16 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.
What to do
Upgrade Linux kernel to 86d13a6f49cb68aa91bd718b1b627e72e77285c1, 4ccdbf50dd88a2a7399409e68887dd8077f6a562 or 2c0a959bebdc1ada13cf9a8242f177c5400299e6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: net/mlx5: HWS, Fix memory leak in hws_pool_buddy_init error path In the error path of hws_pool_buddy_init(), the buddy allocator cleanup doesn't free the allocator structure itself, causing a memory leak. Add the missing kfree() to properly release all allocated memory.