LiveActive security incident?Get immediate response
CVE Record

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

In the Linux kernel, the following vulnerability has been resolved: crypto: ccp - Fix crash when rebind ccp device for ccp.ko When CONFIG_CRYPTO_DEV_CCP_DEBUGFS 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: error_code(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] start_creating+0x9f/0x1c0 [ 205.001533] debugfs_create_dir+0x1f/0x170 [ 205.002769] ? srso_return_thunk+0x5/0x5f [ 205.004000] ccp5_debugfs_setup+0x87/0x170 [ccp] [ 205.005241] ccp5_init+0x8b2/0x960 [ccp] [ 205.006469] ccp_dev_init+0xd4/0x150 [ccp] [ 205.007709] sp_init+0x5f/0x80 [ccp] [ 205.008942] sp_pci_probe+0x283/0x2e0 [ccp] [ 205.010165] ? srso_return_thunk+0x5/0x5f [ 205.011376] local_pci_probe+0x4f/0xb0 [ 205.012584] pci_device_probe+0xdb/0x230 [ 205.013810] really_probe+0xed/0x380 [ 205.015024] __driver_probe_device+0x7e/0x160 [ 205.016240] device_driver_attach+0x2f/0x60 [ 205.017457] bind_store+0x7c/0xb0 [ 205.018663] drv_attr_store+0x28/0x40 [ 205.019868] sysfs_kf_write+0x5f/0x70 [ 205.021065] kernfs_fop_write_iter+0x145/0x1d0 [ 205.022267] vfs_write+0x308/0x440 [ 205.023453] ksys_write+0x6d/0xe0 [ 205.024616] __x64_sys_write+0x1e/0x30 [ 205.025778] x64_sys_call+0x16ba/0x2150 [ 205.026942] do_syscall_64+0x56/0x1e0 [ 205.028108] entry_SYSCALL_64_after_hwframe+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 ccp_debugfs_dir to NULL after destroying it in ccp5_debugfs_destroy, allowing the directory dentry to be recreated when rebinding the ccp device. Tested on AMD Ryzen 7 1700X.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-38581 is a Linux kernel reliability flaw in the AMD CCP crypto driver. On kernels built with CCP debugfs support, rebinding the CCP PCI device can trigger a kernel NULL pointer dereference and crash the system. The sources show a kernel fix, but no KEV listing or cited active exploitation.

Executive priority

Prioritize patching on AMD-based Linux hosts where kernel crashes would disrupt production workloads. This is not currently evidenced as internet-exploited, but it can cause system instability when the affected driver path is exercised.

Technical view

The bug occurs in ccp.ko when CONFIG_CRYPTO_DEV_CCP_DEBUGFS is enabled. After debugfs teardown, ccp_debugfs_dir was not cleared, so a later device rebind could reuse invalid state while recreating debugfs entries, leading to an oops in debugfs_create_dir. The fix sets ccp_debugfs_dir to NULL after destruction.

Likely exposure

Exposure is mainly Linux systems using affected kernels, AMD CCP hardware/driver support, and builds with CONFIG_CRYPTO_DEV_CCP_DEBUGFS enabled. Practical triggering appears tied to local device unbind and bind operations through sysfs, which usually require elevated administrative control.

Exploitation context

The source bundle documents a reproducible crash during CCP PCI device rebind and marks KEV as false. It does not show remote exploitation, privilege escalation, public weaponization, or active exploitation. Treat this primarily as a local denial-of-service and operational stability issue unless vendor advisories add more evidence.

Researcher notes

The affected data is version-oriented and commit references are provided, but the bundle does not include CVSS, CWE, or detailed downstream package mapping. Validation should focus on kernel lineage, CCP driver presence, debugfs configuration, and whether the stable patch was backported by the distribution.

Mitigation direction

  • Apply vendor kernel updates containing the referenced stable fixes.
  • Review Debian LTS advisories if running Debian LTS kernels.
  • Avoid CCP device rebinding on affected systems until patched.
  • Restrict administrative access to device-management sysfs paths.
  • For custom kernels, review whether CCP debugfs support is required.

Validation and detection

  • Inventory kernels against the affected version information in the CVE record.
  • Confirm AMD CCP driver usage on systems with relevant hardware.
  • Check whether CONFIG_CRYPTO_DEV_CCP_DEBUGFS is enabled in custom builds.
  • Verify vendor kernel packages include the ccp_debugfs_dir cleanup fix.
  • Review crash logs for CCP rebind-related NULL pointer dereferences.
Prepared
Confidence
medium
Sources
12

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-38581 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
12Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux3cdbe346ed3f380eae1cb3e9febfe703e7d8a7b0, 3cdbe346ed3f380eae1cb3e9febfe703e7d8a7b0, 3cdbe346ed3f380eae1cb3e9febfe703e7d8a7b0, 3cdbe346ed3f380eae1cb3e9febfe703e7d8a7b0, 3cdbe346ed3f380eae1cb3e9febfe703e7d8a7b0, 3cdbe346ed3f380eae1cb3e9febfe703e7d8a7b0, 3cdbe346ed3f380eae1cb3e9febfe703e7d8a7b0, 3cdbe346ed3f380eae1cb3e9febfe703e7d8a7b0, 3cdbe346ed3f380eae1cb3e9febfe703e7d8a7b0unaffected
LinuxLinux4.13, 0, 5.4.297, 5.10.241, 5.15.190, 6.1.148, 6.6.102, 6.12.42, 6.15.10, 6.16.1, 6.17affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.