doc/nrf/changelog-known_issues: added records on NCSDK-33173

Added note on fix for following issue:
MCUboot might fail on booting an application when LTO is enabled.

Signed-off-by: Andrzej Puzdrowski <[email protected]>
Signed-off-by: Pekka Niskanen <[email protected]>

Author: nvlsianpu

doc/nrf/releases_and_maturity/known_issues.rst

@@ -4156,6 +4156,17 @@ NCSDK-15494: Unable to build with RSA and ECIES-X25519 image encryptions
 Recovery with the USB does not work
   The MCUboot recovery feature using the USB interface does not work.
 
+.. rst-class:: v3-0-2 v3-0-1 v3-0-0 v2-9-1 v2-9-0 v2-8-0 v2-7-0
+
+NCSDK-33173: MCUboot might fail on booting an application when LTO is enabled
+  The MCUboot might fail on booting an application when it is built with Link Time Optimization enabled.
+  This issue is transient and affects only some MCUboot builds for which it is 100% reproducible.
+
+  **Affected platforms:** All ARM Cortex-M nRF CPUs
+
+  **Workaround:** To fix the issue, update the ``sdk-mcuboot`` repository by cherry-picking the upstream commits with the following hash: ``766081bd6dfe26057fdbe3dca5d8eb5f64681beb``
+
+
 nrfxlib
 *******
 

doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst

@@ -630,7 +630,8 @@ The code for integrating MCUboot into |NCS| is located in the :file:`ncs/nrf/mod
 
 The following list summarizes both the main changes inherited from upstream MCUboot and the main changes applied to the |NCS| specific additions:
 
-|no_changes_yet_note|
+
+* Fixed an issue related to referencing the ARM Vector table of the application, which causes jumping to wrong address instead of the application reset vector for some builds when Zephyr LTO (Link Time Optimization) was enabled.
 
 Zephyr
 ======