CVE-2025-71150 json
ksmbd: Fix refcount leak when invalid session is found on session lookup
published 9mo ago modified 3mo ago also EUVD-2026-4404
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 20%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: Fix refcount leak when invalid session is found on session lookup
When a session is found but its state is not SMB2_SESSION_VALID, It indicates that no valid session was found, but it is missing to decrement the reference count acquired by the session lookup, which results in a reference count leak. This patch fixes the issue by explicitly calling ksmbd_user_session_put to release the reference to the session.
Patch / fix
- Linux Linux 5.15.203, 6.1.160, 6.6.120, 6.12.64, 6.18.3, 6.19
- linux Debian 12 6.1.162-1
- linux Debian 13 6.12.69-1
- linux Debian 14 6.18.3-1
debian advisories DEBIAN-CVE-2025-71150
- linux Ubuntu 22.04 LTS 5.15.0-186.196
- linux Ubuntu 24.04 LTS 6.8.0-110.110
- linux Ubuntu 25.10 6.17.0-22.22
- linux-aws Ubuntu 22.04 LTS 5.15.0-1112.119
- linux-aws Ubuntu 24.04 LTS 6.8.0-1052.55
- linux-aws Ubuntu 25.10 6.17.0-1012.12
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1112.122
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1054.57
ubuntu advisories UBUNTU-CVE-2025-71150
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/11fe566b442e3bc2774191740fd377739a87a1c0 commit
- git.kernel.org/stable/c/0fb87b28cafae71e9c8248432cc3a6a1fd759efc commit
- git.kernel.org/stable/c/e54fb2a4772545701766cba08aab20de5eace8cd commit
- git.kernel.org/stable/c/02e06785e85b4bd86ef3d23b7c8d87acc76773d5 commit
- git.kernel.org/stable/c/8cabcb4dd3dc85dd83a37d26efcc59a66a4074d7 commit
- git.kernel.org/stable/c/cafb57f7bdd57abba87725eb4e82bbdca4959644 commit
Is CVE-2025-71150 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-71150 updated cvss 5.5
kernel: Linux kernel ksmbd: Denial of Service via reference count leak
-
Red Hat Enterprise Linux 10 kernelaffected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.28% chance of exploitation in the next 30 days, higher than 20% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/11fe566b442e3bc2774191740fd377739a87a1c0
-
git.kernel.org
/stable/c/0fb87b28cafae71e9c8248432cc3a6a1fd759efc
patch
-
git.kernel.org
/stable/c/e54fb2a4772545701766cba08aab20de5eace8cd
patch
-
git.kernel.org
/stable/c/02e06785e85b4bd86ef3d23b7c8d87acc76773d5
patch
-
git.kernel.org
/stable/c/8cabcb4dd3dc85dd83a37d26efcc59a66a4074d7
patch
-
git.kernel.org
/stable/c/cafb57f7bdd57abba87725eb4e82bbdca4959644
patch
Sources
- CVE List CVE-2025-71150
- NVD CVE-2025-71150
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.