Bug 2523147 - CVE-2026-72714 rocq: Rocq Prover: Critical integrity bypass via universe checking state desynchronization. [fedora-all]
Summary: CVE-2026-72714 rocq: Rocq Prover: Critical integrity bypass via universe chec...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: rocq
Version: rawhide
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Jerry James
QA Contact:
URL:
Whiteboard: {"flaws": ["256382ba-8901-480c-8927-f...
Depends On:
Blocks: CVE-2026-72714
TreeView+ depends on / blocked
 
Reported: 2026-08-24 20:52 UTC by Vladimir Vasilev
Modified: 2026-10-07 01:40 UTC (History)
1 user (show)

Fixed In Version: rocq-9.3.0-2.fc45 rocq-9.3.0-1.fc44
Clone Of:
Environment:
Last Closed: 2026-10-06 00:18:12 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Vladimir Vasilev 2026-08-24 20:52:50 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

Rocq Prover does not restore the universe graph's copy of the universe checking flag when a module that locally disabled the check is closed. Local Unset Universe Checking inside a module is expected to last only until the module ends, and the global flag is restored, but the universe graph keeps its own copy which is left disabled. The two views then disagree: Test Universe Checking reports the check as enabled while the kernel continues to accept universe-inconsistent terms. With the constraint between two universes no longer enforced, Hurkens' paradox applies and yields a proof of False, from which any proposition follows. The proof uses no axioms, plugins or unsafe features once the module has closed, and Print Assumptions reports it as closed under the global context, so neither the assumption audit nor the flag query reflects the actual kernel state. No fix is available.

Comment 1 Fedora Update System 2026-10-03 21:26:40 UTC
FEDORA-2026-403bcf6fd8 (0install-2.18-16.fc45, alt-ergo-2.4.3-5.fc45, and 207 more) has been submitted as an update to Fedora 45.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-403bcf6fd8

Comment 2 Fedora Update System 2026-10-04 03:07:12 UTC
FEDORA-2026-403bcf6fd8 has been pushed to the Fedora 45 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-403bcf6fd8`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-403bcf6fd8

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 3 Fedora Update System 2026-10-05 22:21:45 UTC
FEDORA-2026-62bbabcf11 (flocq-4.2.2-3.fc44, gappalib-coq-1.11.0-1.fc44, and 4 more) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-62bbabcf11

Comment 4 Fedora Update System 2026-10-06 00:18:12 UTC
FEDORA-2026-403bcf6fd8 (0install-2.18-16.fc45, alt-ergo-2.4.3-5.fc45, and 207 more) has been pushed to the Fedora 45 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 5 Fedora Update System 2026-10-06 01:57:28 UTC
FEDORA-2026-62bbabcf11 has been pushed to the Fedora 44 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-62bbabcf11`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-62bbabcf11

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2026-10-07 01:40:50 UTC
FEDORA-2026-62bbabcf11 (flocq-4.2.2-3.fc44, gappalib-coq-1.11.0-1.fc44, and 4 more) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.