On All Junos Platforms enabling monitor traffic interface enabled on loopback can lead to kernel crash in rare timing scenario.

vmcore will be seen, post system crash

lab@xxx> show version detail no-forwarding
Hostname:XXX
Model: mx480
Junos: 22.4R1-S2.1

lab@xxx> show chassis routing-engine no-forwarding

Routing Engine status:
  Slot 0:
    Current state                  Master
    Election priority              Master (default)
    Temperature                 33 degrees C / 91 degrees F
    CPU temperature             30 degrees C / 86 degrees F
    DRAM                      16315 MB (16384 MB installed)
    Memory utilization          71 percent
    Model                          RE-S-1800x4
    Serial ID                      9009211977
    Start time                     2023-07-03 10:21:29 
    Uptime                         1 hour, 4 minutes, 52 seconds
    Last reboot reason             0x100:reset from debugger
    Load averages:                 1 minute   5 minute  15 minute
                                       0.45       0.61       0.91

lab@xxx> show system core-dumps no-forwarding
-rw-------  1 root  wheel  1630928896 Jul 3  10:24 /var/crash/vmcore.0
lrwxr-xr-x  1 root  wheel          8 Jul 3  10:24 /var/crash/vmcore.last@ -> vmcore.0

Workaround:
Do not enable monitor traffic/tcpdump on the loopback interface.

https://prsearch.juniper.net/PR1753908
Need to take the fix of above PR.
Resolved-In
junos:20.3X75-D52 junos:20.4R3-S10 junos:21.2R3-S8 junos:22.1R3-S5 junos:22.2R3-S3 junos:22.3R3-S2 junos:22.4R3 junos:23.2R2 junos:23.4R1 junos:24.1R1