CVE-2023-5178
A public proof of concept exists; no exploitation attested.
- Published2023-11-01
- Fixed in6.5.9 · 6.1.60 · 5.15.137 · 5.10.199 · 5.4.260
- WeaknessCWE-416
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
A use-after-free vulnerability was found in drivers/nvme/target/tcp.c` in `nvmet_tcp_free_crypto` due to a logical bug in the NVMe/TCP subsystem in the Linux kernel. This issue may allow a malicious user to cause a use-after-free and double-free problem, which may permit remote code execution or lead to local privilege escalation.
Timeline
dates in UTC- 2023-11-0117:15CVE publishedNVD
- 2026-10-2319:23First public proof of conceptPoC-in-GitHub
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2023-5178?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2023-5178?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 6.x | ≥ 6.2, < 6.5.9 | 6.5.9 | NVD |
| 6.1 | ≥ 5.16, < 6.1.60 | 6.1.60 | NVD |
| 5.x | ≥ 5.11, < 5.15.137 | 5.15.137 | NVD |
| 5.x | ≥ 5.5, < 5.10.199 | 5.10.199 | NVD |
| 5.x | ≥ 5.0, < 5.4.260 | 5.4.260 | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 8.0 | = 8.0 | no fix published | NVD |
| 9.0 | = 9.0 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| — | all versions | no fix published | NVD |
2 more products in the sources.
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Packages
- kernelAlmaLinux:8all versions · fixed in 4.18.0-513.9.1.el8_9and 23 other packages
Fix
- Update Linux linux kernel to 6.5.9 · 6.1.60 · 5.15.137 · 5.10.199 · 5.4.260
Advisories and patches
- lore.kernel.orgPatch · Vendor Advisory
Detection
read 2026-10-23 19:23 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
Sources
- CNACVSS 3.18.8read 2026-10-23
- NVDCVSS 3.18.8read 2026-10-23
- CNAweakness (CWE)CWE-416read 2026-10-23
- NVDweakness (CWE)CWE-416read 2026-10-23
- FIRST EPSSEPSS score9.6 %2026-10-23
- PoC-in-GitHubproof of concept1read 2026-10-23
- OSVaffected packages—
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Published
- 2023-11-01
- Last Modified
- 2026-10-14
- NVD status
- Modified
Frequently asked questions
What is CVE-2023-5178?
Is CVE-2023-5178 actively exploited?
What is the CVSS score for CVE-2023-5178?
Running Linux kernel? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.