---
id: CVE-2025-39819
title: 'fs/smb: Fix inconsistent refcnt update'
summary: >-
  In the Linux kernel, the following vulnerability has been resolved:


  fs/smb: Fix inconsistent refcnt update


  A possible inconsistent update of refcount was identified in
  `smb2_compound_op`.

  Such inconsistent update could lead to possible…
severity: none
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= a7d5c294628088781da9e91cbb034d61c3a71f71 <
    3fc11ff13fbc2749871d6ac2141685cf54699997
  - >-
    Linux >= a7d5c294628088781da9e91cbb034d61c3a71f71 <
    4191ea1f0bb3e27d65c5dcde7bd00e709ec67141
  - >-
    Linux >= a7d5c294628088781da9e91cbb034d61c3a71f71 <
    4735f5991f51468b85affb8366b7067248457a71
  - >-
    Linux >= a7d5c294628088781da9e91cbb034d61c3a71f71 <
    cc82c6dff548f0066a51a6e577c7454e7d26a968
  - >-
    Linux >= a7d5c294628088781da9e91cbb034d61c3a71f71 <
    ab529e6ca1f67bcf31f3ea80c72bffde2e9e053e
  - Linux 5.8
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: partial
  timestamp: '2026-11-05T21:12:09.908513Z'
published: '2025-09-16'
updated: '2026-11-05'
sourceUpdated: '2026-11-05T21:12:59.279Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2025-39819'
references:
  - url: 'https://git.kernel.org/stable/c/3fc11ff13fbc2749871d6ac2141685cf54699997'
  - url: 'https://git.kernel.org/stable/c/4191ea1f0bb3e27d65c5dcde7bd00e709ec67141'
  - url: 'https://git.kernel.org/stable/c/4735f5991f51468b85affb8366b7067248457a71'
  - url: 'https://git.kernel.org/stable/c/cc82c6dff548f0066a51a6e577c7454e7d26a968'
  - url: 'https://git.kernel.org/stable/c/ab529e6ca1f67bcf31f3ea80c72bffde2e9e053e'
tags:
  - cve.org
epss: 0.0015
epssPercentile: 0.04188
ingestedAt: '2026-11-05T22:38:32.031Z'
---

## Overview

In the Linux kernel, the following vulnerability has been resolved:

fs/smb: Fix inconsistent refcnt update

A possible inconsistent update of refcount was identified in `smb2_compound_op`.
Such inconsistent update could lead to possible resource leaks.

Why it is a possible bug:
1. In the comment section of the function, it clearly states that the
reference to `cfile` should be dropped after calling this function.
2. Every control flow path would check and drop the reference to
`cfile`, except the patched one.
3. Existing callers would not handle refcount update of `cfile` if
-ENOMEM is returned.

To fix the bug, an extra goto label "out" is added, to make sure that the
cleanup logic would always be respected. As the problem is caused by the
allocation failure of `vars`, the cleanup logic between label "finished"
and "out" can be safely ignored. According to the definition of function
`is_replayable_error`, the error code of "-ENOMEM" is not recoverable.
Therefore, the replay logic also gets ignored.

## Affected

- `Linux >= a7d5c294628088781da9e91cbb034d61c3a71f71 < 3fc11ff13fbc2749871d6ac2141685cf54699997`
- `Linux >= a7d5c294628088781da9e91cbb034d61c3a71f71 < 4191ea1f0bb3e27d65c5dcde7bd00e709ec67141`
- `Linux >= a7d5c294628088781da9e91cbb034d61c3a71f71 < 4735f5991f51468b85affb8366b7067248457a71`
- `Linux >= a7d5c294628088781da9e91cbb034d61c3a71f71 < cc82c6dff548f0066a51a6e577c7454e7d26a968`
- `Linux >= a7d5c294628088781da9e91cbb034d61c3a71f71 < ab529e6ca1f67bcf31f3ea80c72bffde2e9e053e`
- `Linux 5.8`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.