Security readout for executives and security teams
Plain-English summary
CVE-2022-50382 is a Linux kernel flaw that can deadlock the system under specific local conditions. It does not expose data or allow code execution, but it can cause availability loss. The issue is in padata handling used by parallel processing paths, including pcrypt crypto work.
Executive priority
Schedule normal-priority patching, with faster action for shared Linux hosts or systems where availability is business-critical. This is not supported as remotely exploitable by the provided sources, but a local denial-of-service can still disrupt production services.
Technical view
The kernel padata current-task path could run ->parallel() with bottom halves enabled. During pcrypt AEAD processing, padata_do_serial could take reorder->lock, then softirq processing could re-enter padata_do_serial and deadlock on the same lock. The fix keeps bottom halves disabled in that path.
Likely exposure
Exposure is mainly Linux systems running affected kernel versions or unpatched vendor kernels containing this padata behavior. Risk is higher where local users, containers, or workloads can trigger relevant kernel crypto or padata paths under load. The bundle does not identify specific distributions.
Exploitation context
The CVSS vector is local, low complexity, low privilege, no user interaction, and availability impact only. KEV is false, and the provided sources do not report active exploitation or public weaponization. Treat this as a local denial-of-service risk, not remote compromise.
Researcher notes
Evidence points to CWE-667 lock handling: bottom halves remained enabled in one padata execution path, allowing softirq re-entry and deadlock on reorder->lock. The affected version data in the bundle is limited and should be reconciled with kernel or distribution patch metadata.
Mitigation direction
- Update to a vendor kernel containing the referenced stable padata fix.
- Check distribution advisories for backported fixes before relying on version numbers alone.
- Prioritize multi-user, container-hosting, and security-sensitive Linux systems.
- Reduce exposure to untrusted local workloads until patched, where operationally feasible.
Validation and detection
- Inventory Linux kernel versions across servers, workstations, and container hosts.
- Confirm whether vendor kernel changelogs include the referenced padata stable commits.
- Identify systems allowing untrusted local users or tenant workloads.
- Track remediation status separately from package version if fixes are backported.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CWE-667: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-50382 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/8e0681dd4eee029eb1d533d06993f7cb091efb73CVE reference
- https://git.kernel.org/stable/c/17afa98bccec4f52203508b3f49b5f948c6fd6acCVE reference
- https://git.kernel.org/stable/c/7337adb20fcc0aebb50eaff2bc5a8dd9a7c6743dCVE reference
- https://git.kernel.org/stable/c/6cfa9e60c0f88fdec6368e081ab968411cc706b1CVE reference
- https://git.kernel.org/stable/c/34c3a47d20ae55b3600fed733bf96eafe9c500d5CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Locking
Improper Locking represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.