CVE-2025-38581: crypto: ccp - Fix crash when rebind ccp device for ccp.ko

Published Aug 19, 2025
·
Updated

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

crypto: ccp - Fix crash when rebind ccp device for ccp.ko

When CONFIGCRYPTODEVCCPDEBUGFS is enabled, rebinding the ccp device causes the following crash:

$ echo '0000:0a:00.2' > /sys/bus/pci/drivers/ccp/unbind $ echo '0000:0a:00.2' > /sys/bus/pci/drivers/ccp/bind

[ 204.976930] BUG: kernel NULL pointer dereference, address: 0000000000000098 [ 204.978026] #PF: supervisor write access in kernel mode [ 204.979126] #PF: errorcode(0x0002) - not-present page [ 204.980226] PGD 0 P4D 0 [ 204.981317] Oops: Oops: 0002 [#1] SMP NOPTI ... [ 204.997852] Call Trace: [ 204.999074] <TASK> [ 205.000297] startcreating+0x9f/0x1c0 [ 205.001533] debugfscreatedir+0x1f/0x170 [ 205.002769] ? srsoreturnthunk+0x5/0x5f [ 205.004000] ccp5debugfssetup+0x87/0x170 [ccp] [ 205.005241] ccp5init+0x8b2/0x960 [ccp] [ 205.006469] ccpdevinit+0xd4/0x150 [ccp] [ 205.007709] spinit+0x5f/0x80 [ccp] [ 205.008942] sppciprobe+0x283/0x2e0 [ccp] [ 205.010165] ? srsoreturnthunk+0x5/0x5f [ 205.011376] localpciprobe+0x4f/0xb0 [ 205.012584] pcideviceprobe+0xdb/0x230 [ 205.013810] reallyprobe+0xed/0x380 [ 205.015024] driverprobedevice+0x7e/0x160 [ 205.016240] devicedriverattach+0x2f/0x60 [ 205.017457] bindstore+0x7c/0xb0 [ 205.018663] drvattrstore+0x28/0x40 [ 205.019868] sysfskfwrite+0x5f/0x70 [ 205.021065] kernfsfopwriteiter+0x145/0x1d0 [ 205.022267] vfswrite+0x308/0x440 [ 205.023453] ksyswrite+0x6d/0xe0 [ 205.024616] x64syswrite+0x1e/0x30 [ 205.025778] x64syscall+0x16ba/0x2150 [ 205.026942] dosyscall64+0x56/0x1e0 [ 205.028108] entrySYSCALL64afterhwframe+0x76/0x7e [ 205.029276] RIP: 0033:0x7fbc36f10104 [ 205.030420] Code: 89 02 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 8d 05 e1 08 2e 00 8b 00 85 c0 75 13 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 54 f3 c3 66 90 41 54 55 49 89 d4 53 48 89 f5

This patch sets ccpdebugfsdir to NULL after destroying it in ccp5debugfsdestroy, allowing the directory dentry to be recreated when rebinding the ccp device.

Tested on AMD Ryzen 7 1700X.

Affected Software

10 affected components
Linux Kernel
Linux Linux kernel>=4.13<5.4.297
Linux Linux kernel>=5.5<5.10.241
Linux Linux kernel>=5.11<5.15.190
Linux Linux kernel>=5.16<6.1.148
Linux Linux kernel>=6.2<6.6.102
Linux Linux kernel>=6.7<6.12.42
Linux Linux kernel>=6.13<6.15.10
Linux Linux kernel>=6.16<6.16.1
Debian Debian Linux=11.0

Event History

Aug 19, 2025
CVE Published
via MITRE·05:03 PM
Data Sourced
via MITRE·05:03 PM
Description
Data Sourced
via NVD·05:15 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-38581?

CVE-2025-38581 is classified as a medium severity vulnerability due to the potential crash it may cause.

2

How do I fix CVE-2025-38581?

To fix CVE-2025-38581, ensure that you apply the latest patches provided for the Linux kernel that address this vulnerability.

3

What does CVE-2025-38581 affect?

CVE-2025-38581 affects the Linux kernel when the CONFIG_CRYPTO_DEV_CCP_DEBUGFS option is enabled.

4

What are the consequences of CVE-2025-38581?

The consequence of CVE-2025-38581 is a crash that occurs when attempting to rebind the ccp device.

5

When was CVE-2025-38581 disclosed?

CVE-2025-38581 was disclosed in 2025 as part of a series of updates to the Linux kernel.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203