Linux Kernel up to 6.17-rc3 net rose_rt_free reference count

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.4 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical was found in Linux Kernel up to 6.1.149/6.6.103/6.12.44/6.16.4/6.17-rc3. Impacted is the function rose_rt_free of the component net. The manipulation results in reference count.
This vulnerability is known as CVE-2025-39827. No exploit is available.
Upgrading the affected component is advised.
Details
A vulnerability classified as problematic has been found in Linux Kernel up to 6.1.149/6.6.103/6.12.44/6.16.4/6.17-rc3. Affected is the function rose_rt_free of the component net. The manipulation with an unknown input leads to a reference count vulnerability. CWE is classifying the issue as CWE-911. The product uses a reference count to manage a resource, but it does not update or incorrectly updates the reference count. This is going to have an impact on availability. CVE summarizes:
In the Linux kernel, the following vulnerability has been resolved: net: rose: include node references in rose_neigh refcount Current implementation maintains two separate reference counting mechanisms: the 'count' field in struct rose_neigh tracks references from rose_node structures, while the 'use' field (now refcount_t) tracks references from rose_sock. This patch merges these two reference counting systems using 'use' field for proper reference management. Specifically, this patch adds incrementing and decrementing of rose_neigh->use when rose_neigh->count is incremented or decremented. This patch also modifies rose_rt_free(), rose_rt_device_down() and rose_clear_route() to properly release references to rose_neigh objects before freeing a rose_node through rose_remove_node(). These changes ensure rose_neigh structures are properly freed only when all references, including those from rose_node structures, are released. As a result, this resolves a slab-use-after-free issue reported by Syzbot.
The advisory is available at git.kernel.org. This vulnerability is traded as CVE-2025-39827 since 04/16/2025. Technical details are known, but there is no available exploit.
The vulnerability scanner Nessus provides a plugin with the ID 265306 (Linux Distros Unpatched Vulnerability : CVE-2025-39827), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 6.1.150, 6.6.104, 6.12.45, 6.16.5 or 6.17-rc4 eliminates this vulnerability. Applying the patch 4cce478c3e82a5fc788d72adb2f4c4e983997639/9c547c8eee9d1cf6e744611d688b9f725cf9a115/d7563b456ed44151e1a82091d96f60166daea89b/384210cceb1873a4c8218b27ba0745444436b728/da9c9c877597170b929a6121a68dcd3dd9a80f45 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 (265306) and CERT Bund (WID-SEC-2025-2077). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Affected
- Debian Linux
- Amazon Linux 2
- Red Hat Enterprise Linux
- Ubuntu Linux
- SUSE Linux
- Oracle Linux
- IBM QRadar SIEM
- SUSE openSUSE
- Open Source Linux Kernel
- RESF Rocky Linux
- Dell Secure Connect Gateway
Product
Type
Vendor
Name
Version
- 6.1.149
- 6.6.103
- 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.12.44
- 6.16.0
- 6.16.1
- 6.16.2
- 6.16.3
- 6.16.4
- 6.17-rc1
- 6.17-rc2
- 6.17-rc3
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.5VulDB Meta Temp Score: 4.4
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
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: Reference countCWE: CWE-911 / CWE-664
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: 265306
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2025-39827
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 6.1.150/6.6.104/6.12.45/6.16.5/6.17-rc4
Patch: 4cce478c3e82a5fc788d72adb2f4c4e983997639/9c547c8eee9d1cf6e744611d688b9f725cf9a115/d7563b456ed44151e1a82091d96f60166daea89b/384210cceb1873a4c8218b27ba0745444436b728/da9c9c877597170b929a6121a68dcd3dd9a80f45
Timeline
04/16/2025 CVE reserved09/16/2025 Advisory disclosed
09/16/2025 VulDB entry created
01/16/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2025-39827 (🔒)
GCVE (CVE): GCVE-0-2025-39827
GCVE (VulDB): GCVE-100-324450
CERT Bund: WID-SEC-2025-2077 - Linux Kernel: Mehrere Schwachstellen
Entry
Created: 09/16/2025 16:08Updated: 01/16/2026 23:47
Changes: 09/16/2025 16:08 (59), 09/17/2025 13:32 (2), 10/21/2025 09:06 (7), 12/27/2025 18:36 (1), 01/16/2026 23:47 (11)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.