CVE-2024-43102: FreeBSD · Use After Free
Affects FreeBSDSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical · fixed in p10 : patch FreeBSD as a priority.
Data as of 4 Nov 2026, 00:28 UTC
Thin evidence
One scorer or none| CISA-ADP | CVSS 3.1 | 9.8 |
|---|
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Total control over the software or total information disclosure
CISA SSVC assessment, 2024-09-13.
- Patch
- Available – fixed in p10, p6, p4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 5 Sep 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.
What to do
Upgrade FreeBSD to p10, p6 or p4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| FreeBSDFreeBSD | Affected
| Fixed in
|
| FreeBSDFreeBSD | Affected
| Fixed in
|
| FreeBSDFreeBSD | Affected
| Fixed in
|
AI-suggested
Apply the official patches provided by FreeBSD: update to patch level p6 for 13.3-RELEASE, p10 for 14.0-RELEASE, and p4 for 14.1-RELEASE or later. These patches fix the reference counting issue and prevent premature freeing of shared memory mappings. No other mitigations are indicated by the vendor advisory.
Description
Concurrent removals of certain anonymous shared memory mappings by using the UMTX_SHM_DESTROY sub-request of UMTX_OP_SHM can lead to decreasing the reference count of the object representing the mapping too many times, causing it to be freed too early. A malicious code exercizing the UMTX_SHM_DESTROY sub-request in parallel can panic the kernel or enable further Use-After-Free attacks, potentially including code execution or Capsicum sandbox escape.