Kernel BUG via atomic-context instance freeing
Published Dec 9, 2025 · Updated May 11, 2026
Improper execution context handling in the Linux kernel Crypto API allows local users to trigger a kernel BUG backtrace. crypto_destroy_instance directly reaches crypto_drop_spawn during instance destruction even though that operation requires process context. Triggering requires an instance to be unregistered with active users and its last user to release it in atomic context; public evidence reports a BUG backtrace, not code execution or data exposure.
Summary
What happened
Improper execution context handling in the Linux kernel Crypto API allows local users to trigger a kernel BUG backtrace. crypto_destroy_instance directly reaches crypto_drop_spawn during instance destruction even though that operation requires process context. Triggering requires an instance to be unregistered with active users and its last user to release it in atomic context; public evidence reports a BUG backtrace, not code execution or data exposure.
The record
- CVE
- CVE-2023-53799
- Published
- Dec 9, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 9, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.6.19
- Affected versionversion=6bfd48096ff8ecabf955958b51ddfa7988eb0a14 <048545d9fc6424b0a11e7e8771225bb9afe09422
- Affected versionversion=6bfd48096ff8ecabf955958b51ddfa7988eb0a14 <625bf86bf53eb7a8ee60fb9dc45b272b77e5ce1c
- Affected versionversion=6bfd48096ff8ecabf955958b51ddfa7988eb0a14 <867a146690960ac7b89ce40f4ee60dd32eeb1682
- Affected versionversion=6bfd48096ff8ecabf955958b51ddfa7988eb0a14 <9ae4577bc077a7e32c3c7d442c95bc76865c0f17
- Affected versionversion=6bfd48096ff8ecabf955958b51ddfa7988eb0a14 <c0dbcebc7f390ec7dbe010dcc22c60f0c6bfc26d
- Affected versionversion=6bfd48096ff8ecabf955958b51ddfa7988eb0a14 <c4cb61c5f976183c07d16b0071f0c60bc212ef1f
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo