LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53799: crypto: api - Use work queue in crypto_destroy_instance

In the Linux kernel, the following vulnerability has been resolved: crypto: api - Use work queue in crypto_destroy_instance The function crypto_drop_spawn expects to be called in process context. However, when an instance is unregistered while it still has active users, the last user may cause the instance to be freed in atomic context. Fix this by delaying the freeing to a work queue.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2023-53799 is a Linux kernel crypto API cleanup bug. A crypto instance can be freed from the wrong execution context when active users remain, risking kernel instability. The public record does not provide CVSS, CWE, exploit impact, or active exploitation evidence.

Executive priority

Track this as a kernel maintenance item with unknown severity. It deserves timely patch validation, especially on shared Linux infrastructure, but the provided evidence does not support emergency exploitation claims.

Technical view

The flaw is in crypto_destroy_instance behavior. crypto_drop_spawn expects process context, but unregistering an instance with active users can let the final user free it in atomic context. The kernel fix delays freeing through a work queue.

Likely exposure

Exposure is limited to Linux systems running affected kernel builds. The source bundle lists Linux kernel versions and stable commits, but exact distro exposure depends on vendor backports and packaged kernel revisions.

Exploitation context

No KEV listing is present, and the supplied sources do not report active exploitation, public exploit code, or a confirmed attack path. Treat exploitation status as unconfirmed.

Researcher notes

The core issue is context safety during crypto instance teardown. Impact is not fully characterized in the supplied record, so validation should focus on affected kernel lineage, stable patch presence, and distro backport status.

Mitigation direction

  • Update Linux kernels using vendor-supported packages that include the stable fix.
  • Check distribution advisories for backported fixes before relying on upstream version numbers.
  • Prioritize shared, multi-user, or untrusted workload systems for kernel maintenance review.
  • Avoid claiming remediation complete until the running kernel contains the relevant stable patch.

Validation and detection

  • Inventory running Linux kernel versions across servers, endpoints, and appliances.
  • Compare packaged kernels against vendor advisories and the referenced stable commits.
  • Confirm rebooted systems are running the updated kernel, not only installed packages.
  • Review kernel crash or warning telemetry for crypto API related instability indicators.
Prepared
Confidence
medium
Sources
8

Public sources used

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-2023-53799 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
0ADP providers
7Source 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux6bfd48096ff8ecabf955958b51ddfa7988eb0a14, 6bfd48096ff8ecabf955958b51ddfa7988eb0a14, 6bfd48096ff8ecabf955958b51ddfa7988eb0a14, 6bfd48096ff8ecabf955958b51ddfa7988eb0a14, 6bfd48096ff8ecabf955958b51ddfa7988eb0a14, 6bfd48096ff8ecabf955958b51ddfa7988eb0a14unaffected
LinuxLinux2.6.19, 0, 5.10.195, 5.15.132, 6.1.53, 6.4.16, 6.5.3, 6.6affected
Weakness

CWE details

No CWE listed

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