---
id: CVE-2024-39493
title: |-
  In the Linux kernel, the following vulnerability has been resolved:

  crypto: qat - Fix ADF_DEV_RESET_SYNC memory leak

  Using completion_done to determine whether the caller has gone
  away only works after a complete call
summary: |-
  In the Linux kernel, the following vulnerability has been resolved:

  crypto: qat - Fix ADF_DEV_RESET_SYNC memory leak

  Using completion_done to determine whether the caller has gone
  away only works after a complete call.  Furthermore it'…
severity: medium
cvss: 5.5
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'
cwe:
  - CWE-401
vendor: linux
product: linux_kernel
affected:
  - 'linux_kernel >= 4.19.312, < 4.19.316'
  - 'linux_kernel >= 5.4.274, < 5.4.278'
  - 'linux_kernel >= 5.10.215, < 5.10.219'
  - 'linux_kernel >= 5.15.154, < 5.15.161'
  - 'linux_kernel >= 6.1.84, < 6.1.94'
  - 'linux_kernel >= 6.6.24, < 6.6.34'
  - 'linux_kernel >= 6.9, < 6.9.5'
patched:
  - linux_kernel 6.9.5
published: '2024-07-10'
updated: '2026-10-15'
sourceUpdated: '2026-10-15T01:18:34.500'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2024-39493'
references:
  - url: 'https://git.kernel.org/stable/c/0ce5964b82f212f4df6a9813f09a0b5de15bd9c8'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/3fb4601e0db10d4fe25e46f3fa308d40d37366bd'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/6396b33e98c096bff9c253ed49c008247963492a'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/a718b6d2a329e069b27d9049a71be5931e71d960'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/c2d443aa1ae3175c13a665f3a24b8acd759ce9c3'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/d0fd124972724cce0d48b9865ce3e273ef69e246'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/d3b17c6d9dddc2db3670bc9be628b122416a3d26'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/e7428e7e3fe94a5089dc12ffe5bc31574d2315ad'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/0ce5964b82f212f4df6a9813f09a0b5de15bd9c8'
    label: af854a3a-2127-422b-91ae-364da2661108
  - url: 'https://git.kernel.org/stable/c/3fb4601e0db10d4fe25e46f3fa308d40d37366bd'
    label: af854a3a-2127-422b-91ae-364da2661108
  - url: 'https://git.kernel.org/stable/c/6396b33e98c096bff9c253ed49c008247963492a'
    label: af854a3a-2127-422b-91ae-364da2661108
  - url: 'https://git.kernel.org/stable/c/a718b6d2a329e069b27d9049a71be5931e71d960'
    label: af854a3a-2127-422b-91ae-364da2661108
  - url: 'https://git.kernel.org/stable/c/c2d443aa1ae3175c13a665f3a24b8acd759ce9c3'
    label: af854a3a-2127-422b-91ae-364da2661108
  - url: 'https://git.kernel.org/stable/c/d0fd124972724cce0d48b9865ce3e273ef69e246'
    label: af854a3a-2127-422b-91ae-364da2661108
  - url: 'https://git.kernel.org/stable/c/d3b17c6d9dddc2db3670bc9be628b122416a3d26'
    label: af854a3a-2127-422b-91ae-364da2661108
  - url: 'https://git.kernel.org/stable/c/e7428e7e3fe94a5089dc12ffe5bc31574d2315ad'
    label: af854a3a-2127-422b-91ae-364da2661108
  - url: 'https://cert-portal.siemens.com/productcert/html/ssa-265688.html'
    label: 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
  - url: 'https://cert-portal.siemens.com/productcert/html/ssa-613116.html'
    label: 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
tags:
  - nvd
  - cve.org
epss: 0.00239
epssPercentile: 0.14894
ingestedAt: '2026-10-15T03:30:12.718Z'
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: partial
  timestamp: '2024-07-10T13:38:46.024569Z'
---

## Overview

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

crypto: qat - Fix ADF_DEV_RESET_SYNC memory leak

Using completion_done to determine whether the caller has gone
away only works after a complete call.  Furthermore it's still
possible that the caller has not yet called wait_for_completion,
resulting in another potential UAF.

Fix this by making the caller use cancel_work_sync and then freeing
the memory safely.

## Affected

- `linux_kernel >= 4.19.312, < 4.19.316`
- `linux_kernel >= 5.4.274, < 5.4.278`
- `linux_kernel >= 5.10.215, < 5.10.219`
- `linux_kernel >= 5.15.154, < 5.15.161`
- `linux_kernel >= 6.1.84, < 6.1.94`
- `linux_kernel >= 6.6.24, < 6.6.34`
- `linux_kernel >= 6.9, < 6.9.5`

## Remediation

Upgrade past the affected range:

- `linux_kernel 6.9.5`