Skip to main content
VulnerabilityPublished Updated

CVE-2025-38031: Linux kernel · padata: do not leak refcount in reorder_work

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in d6ebcde6d4ecf34f8495fb30516645db3aea8993 : update Linux kernel when convenient.

Data as of 5 Nov 2026, 21:04 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch
Available – fixed in d6ebcde6d4ecf34f8495fb30516645db3aea8993, cceb15864e1612ebfbc10ec4e4dcd19a10c0056c, b9ad8e50e8589607e68e6c4cefa7f72bf35a2cb1 +10

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • >=5.10.235 <5.10.238
  • >=5.15.179 <5.15.185
  • >=6.1.129 <6.1.141
  • >=6.6.76 <6.6.93
  • >=6.12.13 <6.12.31
  • >=6.13.2 <6.14
Fixed in
  • d6ebcde6d4ecf34f8495fb30516645db3aea8993
  • cceb15864e1612ebfbc10ec4e4dcd19a10c0056c
  • b9ad8e50e8589607e68e6c4cefa7f72bf35a2cb1
  • 5300e487487d7a2e3e1e6e9d8f03ed9452e4019e
  • 584a729615fa92f4de45480efb7e569d14be1516
  • 6.14
  • 6.12.31
  • 6.6.93
  • 6.1.141
  • 5.15.185
  • 5.10.238
  • 1c65ae4988714716101555fe2b9830e33136d6fb
  • 1a426abdf1c86882c9203dd8182f3b8274b89938
LinuxLinuxAffected
  • =6.14
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: padata: do not leak refcount in reorder_work A recent patch that addressed a UAF introduced a reference count leak: the parallel_data refcount is incremented unconditionally, regardless of the return value of queue_work(). If the work item is already queued, the incremented refcount is never decremented. Fix this by checking the return value of queue_work() and decrementing the refcount when necessary. Resolves: Unreferenced object 0xffff9d9f421e3d80 (size 192): comm "cryptomgr_probe", pid 157, jiffies 4294694003 hex dump (first 32 bytes): 80 8b cf 41 9f 9d ff ff b8 97 e0 89 ff ff ff ff ...A............ d0 97 e0 89 ff ff ff ff 19 00 00 00 1f 88 23 00 ..............#. backtrace (crc 838fb36): __kmalloc_cache_noprof+0x284/0x320 padata_alloc_pd+0x20/0x1e0 padata_alloc_shell+0x3b/0xa0 0xffffffffc040a54d cryptomgr_probe+0x43/0xc0 kthread+0xf6/0x1f0 ret_from_fork+0x2f/0x50 ret_from_fork_asm+0x1a/0x30

References

Community reviews

Loading reviews…