Skip to content
Fencer Vulns
no cvss —

OSEC-2026-30 json

Ephemeron data is freed while still referenced when the key is an `Infix_tag` closure

published 2026-11-06 2 d ago modified 2026-11-06 2 d ago

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

## Summary

In OCaml before 4.14.5, when the key of an ephemeron is a closure with `Infix_tag` (a function of a mutually recursive group that is not the first function), the mark phase does not keep the ephemeron's data alive, although the key is alive. The clean phase does treat the key as alive, so it leaves the data field filled. The sweep phase then frees the data block. After a major collection the ephemeron's data field still points to the freed block.

This looks like the part of [#7810](https://github.com/ocaml/ocaml/issues/7810) that PR [#9742](https://github.com/ocaml/ocaml/pull/9742) did not cover. PR [#9742](https://github.com/ocaml/ocaml/pull/9742) fixed the clean phase and the minor collector. It did not change `mark_ephe_aux`.

Please note that the CVSS score high is under the conditions: - *if* the application is using ephemerons, - and *if* the application is available over the network, - and *if* the attacker can find a way to exploit the memory safety issue in an attack chain.

## Reproduction

```ocaml [@@@alert "-old_ephemeron_api"] let infix n = let rec f () = n and g () = f () in g

let build key n = let e = Ephemeron.K1.create () in let w = Weak.create 1 in let d = ref n in Ephemeron.K1.set_key e key; Ephemeron.K1.set_data e d; Weak.set w 0 (Some d); (e, w)

let run key = let (e, w) = build key 1 in Gc.full_major (); Printf.printf "tag=%d weak=%b check_key=%b check_data=%b\n" (Obj.tag (Obj.repr key)) (Weak.check w 0) (Ephemeron.K1.check_key e) (Ephemeron.K1.check_data e); ignore (Sys.opaque_identity key)

let () = if Sys.argv.(1) = "infix" then run (infix 1) else run (ref 1) ```

`Obj` is used only to print the tag of the key. The program does not read the data after the collection.

## Timeline

- 2026-10-04: initial report via email - 2026-10-09: develop and committed the fix - 2026-11-03: fix was reviewed and merged - 2026-11-06: OCaml 4.14.5 released

Patch / fix

  • opam ocaml 4.14.5

Affected packages

ecosystem package affected fixed in
opam ocaml
<4.14.5
4.14.5

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.