Linux Kernel up to 6.1.148/6.6.102/6.12.43/6.16.3 __get_user comparison

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Linux Kernel up to 6.1.148/6.6.102/6.12.43/6.16.3. It has been rated as critical. Affected by this issue is the function __get_user. Performing a manipulation results in comparison.
This vulnerability is reported as CVE-2025-39716. No exploit exists.
Upgrading the affected component is advised.
Details
A vulnerability was found in Linux Kernel up to 6.1.148/6.6.102/6.12.43/6.16.3. It has been classified as critical. This affects the function __get_user. The manipulation with an unknown input leads to a comparison vulnerability. CWE is classifying the issue as CWE-697. The product compares two entities in a security-relevant context, but the comparison is incorrect, which may lead to resultant weaknesses. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: parisc: Revise __get_user() to probe user read access Because of the way read access support is implemented, read access interruptions are only triggered at privilege levels 2 and 3. The kernel executes at privilege level 0, so __get_user() never triggers a read access interruption (code 26). Thus, it is currently possible for user code to access a read protected address via a system call. Fix this by probing read access rights at privilege level 3 (PRIV_USER) and setting __gu_err to -EFAULT (-14) if access isn't allowed. Note the cmpiclr instruction does a 32-bit compare because COND macro doesn't work inside asm.
The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2025-39716 since 04/16/2025. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 02/09/2026).
The vulnerability scanner Nessus provides a plugin with the ID 261646 (Linux Distros Unpatched Vulnerability : CVE-2025-39716), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 6.1.149, 6.6.103, 6.12.44, 6.16.4 or 6.17-rc1 eliminates this vulnerability. Applying the patch 28a9b71671fb4a2993ef85b8ef6f117ea63894fe/4c981077255acc2ed5b3df6e8dd0125c81b626a9/f410ef9a032caf98117256b22139c31342d7bb06/741b163e440683195b8fd4fc8495fcd0105c6ab7/89f686a0fb6e473a876a9a60a13aec67a62b9a7e is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the databases at Tenable (261646), EUVD (EUVD-2025-31511) and CERT Bund (WID-SEC-2025-1988). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Debian Linux
- Google Cloud Platform
- Amazon Linux 2
- Red Hat Enterprise Linux
- Ubuntu Linux
- SUSE Linux
- Oracle Linux
- NetApp FAS
- NetApp AFF
- NetApp ActiveIQ Unified Manager
- SUSE openSUSE
- RESF Rocky Linux
- Open Source Linux Kernel
- Microsoft Azure
- Dell Secure Connect Gateway
- IBM QRadar SIEM
- IBM Security Verify Access
- Dell NetWorker
Product
Type
Vendor
Name
Version
- 6.1.148
- 6.6.102
- 6.12.0
- 6.12.1
- 6.12.2
- 6.12.3
- 6.12.4
- 6.12.5
- 6.12.6
- 6.12.7
- 6.12.8
- 6.12.9
- 6.12.10
- 6.12.11
- 6.12.12
- 6.12.13
- 6.12.14
- 6.12.15
- 6.12.16
- 6.12.17
- 6.12.18
- 6.12.19
- 6.12.20
- 6.12.21
- 6.12.22
- 6.12.23
- 6.12.24
- 6.12.25
- 6.12.26
- 6.12.27
- 6.12.28
- 6.12.29
- 6.12.30
- 6.12.31
- 6.12.32
- 6.12.33
- 6.12.34
- 6.12.35
- 6.12.36
- 6.12.37
- 6.12.38
- 6.12.39
- 6.12.40
- 6.12.41
- 6.12.42
- 6.12.43
- 6.16.0
- 6.16.1
- 6.16.2
- 6.16.3
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.6
VulDB Base Score: 8.0
VulDB Temp Score: 7.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: ComparisonCWE: CWE-697
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 261646
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2025-39716
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 6.1.149/6.6.103/6.12.44/6.16.4/6.17-rc1
Patch: 28a9b71671fb4a2993ef85b8ef6f117ea63894fe/4c981077255acc2ed5b3df6e8dd0125c81b626a9/f410ef9a032caf98117256b22139c31342d7bb06/741b163e440683195b8fd4fc8495fcd0105c6ab7/89f686a0fb6e473a876a9a60a13aec67a62b9a7e
Timeline
04/16/2025 CVE reserved09/05/2025 Advisory disclosed
09/05/2025 VulDB entry created
02/09/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2025-39716 (🔒)
GCVE (CVE): GCVE-0-2025-39716
GCVE (VulDB): GCVE-100-322917
EUVD: 🔒
CERT Bund: WID-SEC-2025-1988 - Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service
Entry
Created: 09/05/2025 21:59Updated: 02/09/2026 19:21
Changes: 09/05/2025 21:59 (58), 09/07/2025 02:11 (2), 11/07/2025 02:47 (7), 11/27/2025 21:54 (1), 01/03/2026 15:02 (1), 01/08/2026 05:05 (11), 01/08/2026 14:47 (1), 01/20/2026 10:08 (1), 02/09/2026 19:21 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.