Skip to main content
VulnerabilityPublished Updated

CVE-2025-39819: Linux kernel · fs/smb: Fix inconsistent refcnt update

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in cc82c6dff548f0066a51a6e577c7454e7d26a968 : update Linux kernel when convenient.

Data as of 5 Nov 2026, 21:35 UTC

Severity
Low

Rated Low by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
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-11-05.

Patch
Available – fixed in cc82c6dff548f0066a51a6e577c7454e7d26a968, ab529e6ca1f67bcf31f3ea80c72bffde2e9e053e, 4735f5991f51468b85affb8366b7067248457a71 +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 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 5 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ a7d5c294628088781da9e91cbb034d61c3a71f71, < cc82c6dff548f0066a51a6e577c7454e7d26a968
Fixed in
  • cc82c6dff548f0066a51a6e577c7454e7d26a968
LinuxLinuxAffected
  • ≥ a7d5c294628088781da9e91cbb034d61c3a71f71, < ab529e6ca1f67bcf31f3ea80c72bffde2e9e053e
Fixed in
  • ab529e6ca1f67bcf31f3ea80c72bffde2e9e053e
LinuxLinuxAffected
  • ≥ a7d5c294628088781da9e91cbb034d61c3a71f71, < 4735f5991f51468b85affb8366b7067248457a71
Fixed in
  • 4735f5991f51468b85affb8366b7067248457a71
LinuxLinuxAffected
  • ≥ a7d5c294628088781da9e91cbb034d61c3a71f71, < 4191ea1f0bb3e27d65c5dcde7bd00e709ec67141
Fixed in
  • 4191ea1f0bb3e27d65c5dcde7bd00e709ec67141
LinuxLinuxAffected
  • ≥ a7d5c294628088781da9e91cbb034d61c3a71f71, < 3fc11ff13fbc2749871d6ac2141685cf54699997
Fixed in
  • 3fc11ff13fbc2749871d6ac2141685cf54699997
LinuxLinuxAffected
  • =5.8
Fixed in–

AI-suggested

This issue has been fixed in the Linux kernel. Users should update to the fixed versions identified by the commits cc82c6dff548f0066a51a6e577c7454e7d26a968, ab529e6ca1f67bcf31f3ea80c72bffde2e9e053e, 4735f5991f51468b85affb8366b7067248457a71, 4191ea1f0bb3e27d65c5dcde7bd00e709ec67141, and 3fc11ff13fbc2749871d6ac2141685cf54699997. The affected version is 5.8. No additional mitigation is required once patched.

Description

A vulnerability in the Linux kernel's SMB filesystem code caused inconsistent reference count updates in the smb2_compound_op function. This flaw could lead to resource leaks due to improper cleanup when memory allocation fails. The issue was fixed by adding a cleanup path to ensure references are properly dropped even on allocation failure.

References

Community reviews

Loading reviews…