1. Home
  2. Vulnerabilities
  3. CVE-2023-53536
0.0
NA
CVE-2023-53536
blk-crypto: make blk_crypto_evict_key() more robust
Description

In the Linux kernel, the following vulnerability has been resolved: blk-crypto: make blk_crypto_evict_key() more robust If blk_crypto_evict_key() sees that the key is still in-use (due to a bug) or that ->keyslot_evict failed, it currently just returns while leaving the key linked into the keyslot management structures. However, blk_crypto_evict_key() is only called in contexts such as inode eviction where failure is not an option. So actually the caller proceeds with freeing the blk_crypto_key regardless of the return value of blk_crypto_evict_key(). These two assumptions don't match, and the result is that there can be a use-after-free in blk_crypto_reprogram_all_keys() after one of these errors occurs. (Note, these errors *shouldn't* happen; we're just talking about what happens if they do anyway.) Fix this by making blk_crypto_evict_key() unlink the key from the keyslot management structures even on failure. Also improve some comments.

INFO

Published Date :

Oct. 4, 2025, 4:15 p.m.

Last Modified :

Oct. 6, 2025, 2:56 p.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2023-53536 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Linux linux_kernel
: Total Affected Vendor : 1 | Products : 1
Solution
Apply the Linux kernel update to fix a use-after-free vulnerability in blk-crypto.
  • Update the Linux kernel to the latest version.
  • Apply the blk-crypto patch.
  • Verify the integrity of the blk_crypto_evict_key function.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2023-53536.

URL Resource
https://git.kernel.org/stable/c/5bb4005fb667c6e2188fa87950f8d5faf2994410
https://git.kernel.org/stable/c/5c62852942667c613de0458fc797c5b8c36112b5
https://git.kernel.org/stable/c/5c7cb94452901a93e90c2230632e2c12a681bc92
https://git.kernel.org/stable/c/64ef787bb1588475163069c2e62fdd8f6c27b1f6
https://git.kernel.org/stable/c/701a8220762ff90615dc91d3543f789391b63298
https://git.kernel.org/stable/c/809a5be62e92a444a3c3d7b9f438019d0b322f55
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2023-53536 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2023-53536 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2023-53536 vulnerability anywhere in the article.

Results are limited to the first 20 news articles due to potential performance issues.

The following table lists the changes that have been made to the CVE-2023-53536 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Oct. 04, 2025

    Action Type Old Value New Value
    Added Description In the Linux kernel, the following vulnerability has been resolved: blk-crypto: make blk_crypto_evict_key() more robust If blk_crypto_evict_key() sees that the key is still in-use (due to a bug) or that ->keyslot_evict failed, it currently just returns while leaving the key linked into the keyslot management structures. However, blk_crypto_evict_key() is only called in contexts such as inode eviction where failure is not an option. So actually the caller proceeds with freeing the blk_crypto_key regardless of the return value of blk_crypto_evict_key(). These two assumptions don't match, and the result is that there can be a use-after-free in blk_crypto_reprogram_all_keys() after one of these errors occurs. (Note, these errors *shouldn't* happen; we're just talking about what happens if they do anyway.) Fix this by making blk_crypto_evict_key() unlink the key from the keyslot management structures even on failure. Also improve some comments.
    Added Reference https://git.kernel.org/stable/c/5bb4005fb667c6e2188fa87950f8d5faf2994410
    Added Reference https://git.kernel.org/stable/c/5c62852942667c613de0458fc797c5b8c36112b5
    Added Reference https://git.kernel.org/stable/c/5c7cb94452901a93e90c2230632e2c12a681bc92
    Added Reference https://git.kernel.org/stable/c/64ef787bb1588475163069c2e62fdd8f6c27b1f6
    Added Reference https://git.kernel.org/stable/c/701a8220762ff90615dc91d3543f789391b63298
    Added Reference https://git.kernel.org/stable/c/809a5be62e92a444a3c3d7b9f438019d0b322f55
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
Vulnerability Scoring Details
No CVSS metrics available for this vulnerability.