Bug 2523145 - CVE-2026-72703 rocq: Rocq Prover: Logical Flaw Allows Arbitrary Proof Generation via Unchecked Cross-Calls [fedora-all]
Summary: CVE-2026-72703 rocq: Rocq Prover: Logical Flaw Allows Arbitrary Proof Generat...
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": ["6f2279d2-2437-4dbd-9983-2...
Depends On:
Blocks: CVE-2026-72703
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:06 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Vladimir Vasilev 2026-08-24 20:52:33 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.

The guard checker in Rocq Prover treats a parameter of a nested mutual fixpoint as uniform without examining calls between the different bodies of that fixpoint. find_uniform_parameters in kernel/inductive.ml inspects only self-recursive calls, so when no body calls itself the function concludes that every parameter is uniform. A parameter that grows through a cross-call from one body to another therefore keeps the subterm specification it inherited from the enclosing fixpoint, and a recursive call guarded by that specification is accepted although the argument is not structurally smaller. A non-terminating definition is admitted as structurally decreasing, which yields a term whose value equals its own successor and so a proof of False, from which any proposition follows. The proof requires no axioms, plugins or unsafe flags and Print Assumptions reports it as closed under the global context. Introduced in Coq 8.20 and fixed in Rocq 9.2.0.

Comment 1 Fedora Update System 2026-10-03 21:26:34 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:08 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:39 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:06 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:23 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:46 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.