Linux Kernel up to 6.15.9/6.16.0 padata_reorder reference count

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.2 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Linux Kernel up to 6.15.9/6.16.0. This vulnerability affects the function padata_reorder. The manipulation leads to reference count.
This vulnerability is traded as CVE-2025-38584. There is no exploit available.
You should upgrade the affected component.
Details
A vulnerability, which was classified as critical, has been found in Linux Kernel up to 6.15.9/6.16.0. This issue affects the function padata_reorder. The manipulation with an unknown input leads to a reference count vulnerability. Using CWE to declare the problem leads to CWE-911. The product uses a reference count to manage a resource, but it does not update or incorrectly updates the reference count. Impacted is availability. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: padata: Fix pd UAF once and for all There is a race condition/UAF in padata_reorder that goes back to the initial commit. A reference count is taken at the start of the process in padata_do_parallel, and released at the end in padata_serial_worker. This reference count is (and only is) required for padata_replace to function correctly. If padata_replace is never called then there is no issue. In the function padata_reorder which serves as the core of padata, as soon as padata is added to queue->serial.list, and the associated spin lock released, that padata may be processed and the reference count on pd would go away. Fix this by getting the next padata before the squeue->serial lock is released. In order to make this possible, simplify padata_reorder by only calling it once the next padata arrives.
The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2025-38584 since 04/16/2025. The exploitation is known to be difficult. Technical details are known, but no exploit is available.
The vulnerability scanner Nessus provides a plugin with the ID 270738 (openSUSE 15 Security Update : kernel (SUSE-SU-2025:03634-1)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 6.15.10, 6.16.1 or 6.17-rc1 eliminates this vulnerability. Applying the patch dbe3e911a59bda6de96e7cae387ff882c2c177fa/cdf79bd2e1ecb3cc75631c73d8f4149be6019a52/71203f68c7749609d7fc8ae6ad054bdedeb24f91 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 (270738) and CERT Bund (WID-SEC-2025-1869). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Affected
- Debian Linux
- Amazon Linux 2
- Red Hat Enterprise Linux
- Ubuntu Linux
- SUSE Linux
- Oracle Linux
- SUSE openSUSE
- RESF Rocky Linux
- Dell Avamar
- Open Source Linux Kernel
- Dell NetWorker
- Dell Secure Connect Gateway
- IBM QRadar SIEM
Product
Type
Vendor
Name
Version
- 6.0
- 6.1
- 6.2
- 6.3
- 6.4
- 6.5
- 6.6
- 6.7
- 6.8
- 6.9
- 6.10
- 6.11
- 6.12
- 6.13
- 6.14
- 6.15
- 6.15.0
- 6.15.1
- 6.15.2
- 6.15.3
- 6.15.4
- 6.15.5
- 6.15.6
- 6.15.7
- 6.15.8
- 6.15.9
- 6.16.0
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.2
VulDB Base Score: 4.8
VulDB Temp Score: 4.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.8
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: 270738
Nessus Name: openSUSE 15 Security Update : kernel (SUSE-SU-2025:03634-1)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 6.15.10/6.16.1/6.17-rc1
Patch: dbe3e911a59bda6de96e7cae387ff882c2c177fa/cdf79bd2e1ecb3cc75631c73d8f4149be6019a52/71203f68c7749609d7fc8ae6ad054bdedeb24f91
Timeline
04/16/2025 CVE reserved08/19/2025 Advisory disclosed
08/19/2025 VulDB entry created
12/15/2025 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2025-38584 (🔒)
GCVE (CVE): GCVE-0-2025-38584
GCVE (VulDB): GCVE-100-320609
CERT Bund: WID-SEC-2025-1869 - Linux Kernel: Mehrere Schwachstellen
Entry
Created: 08/19/2025 19:29Updated: 12/15/2025 22:58
Changes: 08/19/2025 19:29 (58), 09/24/2025 20:22 (7), 10/18/2025 17:25 (2), 10/27/2025 00:47 (1), 11/01/2025 14:03 (1), 11/26/2025 19:44 (12), 12/15/2025 22:58 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.