The vulnerability arises because MCUboot, in its bare upstream configuration, assumes the system is bootable if at least one slot per image exists, without verifying that the slots for different images match or are authenticated. This can cause the main application to boot from one slot and subsequently start the radio core from a different, unauthenticated slot. This improper verification of cryptographic signatures (CWE-347) can lead to execution of unauthorized code on the affected device.

Successful exploitation could allow an attacker to cause the device to run unauthorized or malicious code by exploiting the lack of proper signature verification between different image slots. This impacts confidentiality, integrity, and availability of the device's operation, as indicated by the CVSS vector (Confidentiality: High, Integrity: High, Availability: High).

No official patch or remediation guidance is currently available from the vendor. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is released, users should be cautious when using the Direct XIP update strategy and consider additional verification mechanisms if possible.