udevadm trigger causes system reset with "watchdog did not stop!" on a system running with Microsoft Defender software.

Issue

• Executing udevadm trigger command causes system reset after reporting watchdog0: watchdog did not stop! message in the logs.
• The issue has also reproducible upon updating a rpm package that has scriptlet to execute udevadm command.
• The system rebooted unexpectedly after running the dnf update command.
• HP system is experiencing an abrupt panic with the following message.

[306693.298556] watchdog: watchdog0: watchdog did not stop!
[306714.419303] Kernel panic - not syncing: 02: An NMI occurred. Depending on your system the reason for the NMI is logged in any one of the following resources:
                1. Integrated Management Log (IML)
                2. OA Syslog
                3. OA Forward Progress Log
                4. iLO Event Log
[306714.419307] CPU: 0 PID: 0 Comm: swapper/0 Kdump: loaded Not tainted 5.14.0-570.19.1.el9_6.x86_64 #1
[306714.419309] Hardware name: HPE ProLiant DL380 Gen10/ProLiant DL380 Gen10, BIOS U30 02/21/2025
[306714.419310] Call Trace:
[306714.419312]  <NMI>
[306714.419320]  dump_stack_lvl+0x34/0x48
[306714.419329]  panic+0x107/0x2bb
[306714.419334]  ? __intel_pmu_enable_all.constprop.0+0x28/0xf0
[306714.419347]  nmi_panic.cold+0xc/0xc
[306714.419349]  hpwdt_pretimeout+0x7f/0xc0 [hpwdt]
[306714.419355]  nmi_handle+0x5b/0x120