CVE-2023-52795: vhost-vdpa: fix use after free in vhost_vdpa_probe()
Noroxi assessment
Priority: Monitor (action score 31/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.24% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux ae8ea4e200675a940c365b496ef8e3fb4123601c, bf04132cd64ccde4e9e9765d489c83fe83c09b7f, c0f8b8fb7df9d1a38652eb5aa817afccd3c56111.
Low priority for now. Upgrade to Linux Linux ae8ea4e200675a940c365b496ef8e3fb4123601c, bf04132cd64ccde4e9e9765d489c83fe83c09b7f, c0f8b8fb7df9d1a38652eb5aa817afccd3c56111 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: vhost-vdpa: fix use after free in vhost_vdpa_probe() The put_device() calls vhost_vdpa_release_dev() which calls ida_simple_remove() and frees "v". So this call to ida_simple_remove() is a use after free and a double free.
- Published
- May 21, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- CWE-415
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
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.
Is your version affected? Check itNoroxi 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
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
- 6.0affected
- ebe6a354fa7e0a7d5b581da31ad031b19d8693f9 and later · before c0f8b8fb7df9d1a38652eb5aa817afccd3c56111affected · git
- ebe6a354fa7e0a7d5b581da31ad031b19d8693f9 and later · before ae8ea4e200675a940c365b496ef8e3fb4123601caffected · git
- ebe6a354fa7e0a7d5b581da31ad031b19d8693f9 and later · before bf04132cd64ccde4e9e9765d489c83fe83c09b7faffected · git
- ebe6a354fa7e0a7d5b581da31ad031b19d8693f9 and later · before e07754e0a1ea2d63fb29574253d1fd7405607343affected · git
- before 6.0not affected · semver
- 6.1.64 and later · up to and including 6.1.*not affected · semver
- 6.5.13 and later · up to and including 6.5.*not affected · semver
- 6.6.3 and later · up to and including 6.6.*not affected · semver
- 6.7 and laternot affected · original_commit_for_fix
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.0 and later · before 6.1.64
- linux linux kernel6.2 and later · before 6.5.13
- linux linux kernel6.6 and later · before 6.6.3
- linux linux kernel6.7
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.64-1 | 6.1.64-1 |
| Debian:13 | linux | before 6.6.8-1 | 6.6.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2023-52792May 21, 2024 · cxl/region: Do not try to cleanup after cxl_region_setup_targets() fails22Monitor
- ← EarlierCVE-2023-52794May 21, 2024 · thermal: intel: powerclamp: fix mismatch in get function for max_idle28Monitor
- Later →CVE-2023-52796May 21, 2024 · ipvlan: add ipvlan_route_v6_outbound() helper31Monitor
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 | ae8ea4e200675a940c365b496ef8e3fb4123601c | Vendor (CNA) |
| Linux Linux | bf04132cd64ccde4e9e9765d489c83fe83c09b7f | Vendor (CNA) |
| Linux Linux | c0f8b8fb7df9d1a38652eb5aa817afccd3c56111 | Vendor (CNA) |
| Linux Linux | e07754e0a1ea2d63fb29574253d1fd7405607343 | Vendor (CNA) |
| debian:linux | 6.1.64-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.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-358144 days apartswiotlb: Fix double-allocation of slots due to broken alignment handling35Monitor
- CVE-2023-528510 days apartIB/mlx5: Fix init stage error handling to avoid double free of same QP and UAF31Monitor
- CVE-2021-474831 days apartregmap: Fix possible double-free in regcache_rbtree_exit()31Monitor
- CVE-2021-475643 days apartnet: marvell: prestera: fix double free issue on err path31Monitor
- CVE-2023-526794 days apartof: Fix double free in of_parse_phandle_with_args_map31Monitor
- CVE-2024-358474 days apartirqchip/gic-v3-its: Prevent double free on error31Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-415 · Double FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.