Mozilla released Firefox 152.0.1 to fix crashes and instability affecting systems with Intel Raptor Lake processors. The failures were tied to a CPU-related issue that appeared during optimized execution paths, including JIT-compiled code and C++ workloads, and Mozilla said a similar mitigation had already been shipped in Firefox 151.0.1.
The reports linked the instability to a specific instruction pattern, mov byte ptr [rsi + rdi + 1], ch, which can be generated by LLVM 22, including for Rust code. Mozilla said the browser update addresses the resulting failures seen on affected Raptor Lake platforms, highlighting a hardware-sensitive problem that surfaced during compilation and runtime optimization.

See real exploitation activity before you spend the cycle.
2 events from the most recent confirmed update back to the earliest known activity.
Mozilla released Firefox 152.0.1 to address crashes and instability associated with Intel Raptor Lake processors. The issue was described as a CPU-related problem affecting optimized execution, including JIT-generated code and C++ workloads, with references to an LLVM 22-generated instruction pattern.
Mozilla said a similar fix for crashes and instability linked to Intel Raptor Lake processors had already been included in Firefox 151.0.1.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See real exploitation activity behind this advisory so you can triage it against everything else in the queue.
3 references tracked. Mallory keeps watching after this page renders.
opennet.me
Open sourceopennet.ru
Open sourcebugzilla.mozilla.org
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.