CVE-2023-53799: crypto: api - Use work queue in crypto_destroy_instance
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Fixed version: Linux Linux 048545d9fc6424b0a11e7e8771225bb9afe09422, 625bf86bf53eb7a8ee60fb9dc45b272b77e5ce1c, 867a146690960ac7b89ce40f4ee60dd32eeb1682.
Low priority for now. Upgrade to Linux Linux 048545d9fc6424b0a11e7e8771225bb9afe09422, 625bf86bf53eb7a8ee60fb9dc45b272b77e5ce1c, 867a146690960ac7b89ce40f4ee60dd32eeb1682 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Dec 8, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.19affected
- 6bfd48096ff8ecabf955958b51ddfa7988eb0a14 and later · before 625bf86bf53eb7a8ee60fb9dc45b272b77e5ce1caffected · git
- 6bfd48096ff8ecabf955958b51ddfa7988eb0a14 and later · before 048545d9fc6424b0a11e7e8771225bb9afe09422affected · git
- 6bfd48096ff8ecabf955958b51ddfa7988eb0a14 and later · before c4cb61c5f976183c07d16b0071f0c60bc212ef1faffected · git
- 6bfd48096ff8ecabf955958b51ddfa7988eb0a14 and later · before 867a146690960ac7b89ce40f4ee60dd32eeb1682affected · git
- 6bfd48096ff8ecabf955958b51ddfa7988eb0a14 and later · before c0dbcebc7f390ec7dbe010dcc22c60f0c6bfc26daffected · git
- 6bfd48096ff8ecabf955958b51ddfa7988eb0a14 and later · before 9ae4577bc077a7e32c3c7d442c95bc76865c0f17affected · git
- before 2.6.19not affected · semver
- 5.10.195 and later · up to and including 5.10.*not affected · semver
- 5.15.132 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.55-1 | 6.1.55-1 |
| Debian:13 | linux | before 6.5.3-1 | 6.5.3-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2023-53797Dec 8, 2025 · HID: wacom: Use ktime_t rather than int when dealing with timestamps28Monitor
- ← EarlierCVE-2023-53798Dec 8, 2025 · ethtool: Fix uninitialized number of lanes0Monitor
- Later →CVE-2023-53801Dec 8, 2025 · iommu/sprd: Release dma buffer to avoid memory leak0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 048545d9fc6424b0a11e7e8771225bb9afe09422 | Vendor (CNA) |
| Linux Linux | 625bf86bf53eb7a8ee60fb9dc45b272b77e5ce1c | Vendor (CNA) |
| Linux Linux | 867a146690960ac7b89ce40f4ee60dd32eeb1682 | Vendor (CNA) |
| Linux Linux | 9ae4577bc077a7e32c3c7d442c95bc76865c0f17 | Vendor (CNA) |
| Linux Linux | c0dbcebc7f390ec7dbe010dcc22c60f0c6bfc26d | Vendor (CNA) |
| Linux Linux | c4cb61c5f976183c07d16b0071f0c60bc212ef1f | Vendor (CNA) |
| debian:linux | 6.1.55-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/625bf86bf53eb7a8ee60fb9dc45b272b77e5ce1c
- git.kernel.org/stable/c/867a146690960ac7b89ce40f4ee60dd32eeb1682
- git.kernel.org/stable/c/9ae4577bc077a7e32c3c7d442c95bc76865c0f17
- git.kernel.org/stable/c/c0dbcebc7f390ec7dbe010dcc22c60f0c6bfc26d
- git.kernel.org/stable/c/c4cb61c5f976183c07d16b0071f0c60bc212ef1f
Vendor advisories and official records. Exploit/PoC links are deliberately left out.