Security context
What an agent needs to avoid regressing past fixes and find the next vuln in this repo.
openjdk/jfx
master @ e84b145
2
Fixes
0
CVEs
HIGH
Peak severity
Highlights
Incomplete Cleanup: 1 prior fix. Scrutinize any change in this area.
JavaScriptCore: most-fixed (2 issues). Treat as high-risk during review.
2 high-severity fixes in this history; regressions here are high-impact.
Recurring patterns
The bug types that recur here, drawn from past fixes, not open vulnerabilities.
Memory Corruption: Underallocation of scratch registers during high-level optimization passes (such as DataView byte length loading in FTLLowerDFGToB3) can result in register clobbering, memory corruption, and potential arbitrary code execution. New JIT optimization paths must rigorously validate physical and scratch register allocation limits.
Incomplete Cleanup: Improper memory alignment of floating-point/double negation constants and incorrect strength reduction optimizations on unaligned shift constants can trigger hardware-level faults or incorrect code generation in the MacroAssembler. Ensuring 16-byte alignment of constants is critical for preventing security-sensitive JIT miscompilations.