Kernel panic via incomplete PADATA_RESET request handling
Published May 21, 2024 · Updated May 11, 2026
A pcrypt concurrency flaw in affected Linux kernels allows local users to trigger a kernel hang and panic during AEAD self-tests. When PADATA_RESET is set, padata_do_parallel returns -EBUSY without invoking aead_request_complete, while test_aead_vec_cfg still waits for completion. Reaching the fault requires local low-privileged access and a concurrent padata reset; the resulting blocked cryptomgr_test task can panic the host.
Summary
What happened
A pcrypt concurrency flaw in affected Linux kernels allows local users to trigger a kernel hang and panic during AEAD self-tests. When PADATA_RESET is set, padata_do_parallel returns -EBUSY without invoking aead_request_complete, while test_aead_vec_cfg still waits for completion. Reaching the fault requires local low-privileged access and a concurrent padata reset; the resulting blocked cryptomgr_test task can panic the host.
The record
- CVE
- CVE-2023-52813
- Published
- May 21, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 21, 2024CVE 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=16295bec6398a3eedc9377e1af6ff4c71b98c300 <039fec48e062504f14845124a1a25eb199b2ddc0
- Affected versionversion=16295bec6398a3eedc9377e1af6ff4c71b98c300 <372636debe852913529b1716f44addd94fff2d28
- Affected versionversion=16295bec6398a3eedc9377e1af6ff4c71b98c300 <546c1796ad1ed0d87dab3c4b5156d75819be2316
- Affected versionversion=16295bec6398a3eedc9377e1af6ff4c71b98c300 <8f4f68e788c3a7a696546291258bfa5fdb215523
- Affected versionversion=16295bec6398a3eedc9377e1af6ff4c71b98c300 <c55fc098fd9d2dca475b82d00ffbcaf97879d77e
- Affected versionversion=16295bec6398a3eedc9377e1af6ff4c71b98c300 <c9c1334697301c10e6918d747ed38abfbc0c96e7
- Affected versionversion=16295bec6398a3eedc9377e1af6ff4c71b98c300 <e134f3aba98e6c801a693f540912c2d493718ddf
- Affected versionversion=16295bec6398a3eedc9377e1af6ff4c71b98c300 <e97bf4ada7dddacd184c3e196bd063b0dc71b41d
- Affected versionversion=16295bec6398a3eedc9377e1af6ff4c71b98c300 <fb2d3a50a8f29a3c66682bb426144f40e32ab818
- Affected versionversion=2.6.34
What conditions does exploitation require?
What is affected?
Published CVSS scores
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
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