diff --git a/doc/nrf/protocols/matter/getting_started/low_power_configuration.rst b/doc/nrf/protocols/matter/getting_started/low_power_configuration.rst
index 20b315a4e7f5..e1773364402a 100644
--- a/doc/nrf/protocols/matter/getting_started/low_power_configuration.rst
+++ b/doc/nrf/protocols/matter/getting_started/low_power_configuration.rst
@@ -16,6 +16,7 @@ The following Matter samples and applications use the low power configuration by
 
 * :ref:`Matter door lock sample <matter_lock_sample>`
 * :ref:`Matter light switch sample <matter_light_switch_sample>`
+* :ref:`Matter smoke CO alarm <matter_smoke_co_alarm_sample>`
 * :ref:`Matter window covering sample <matter_window_covering_sample>`
 * :ref:`Matter weather station application <matter_weather_station_app>`
 
@@ -153,6 +154,18 @@ Switching the Matter :ref:`ug_matter_device_low_power_icd_modes` and frequently
 To avoid this issue, set the :kconfig:option:`CONFIG_CHIP_ICD_SLOW_POLL_INTERVAL` and :kconfig:option:`CONFIG_CHIP_ICD_FAST_POLLING_INTERVAL` Kconfig options to the same value (for example, ``500``).
 The typical use case that the SSED is best suited for is battery-powered devices that require short response time, such as door locks or window blinds.
 
+Child timeouts configuration
+----------------------------
+
+The device working in a Thread child role uses additional mechanisms for periodically ensuring that the communication with the parent is still possible.
+These mechanisms lead to waking up the device and exchanging the messages with the parent, if the related timeout expires.
+In case of using the SED poll period value greater than any of these timeouts, the device wakes up more often than what is defined by the poll period.
+To ensure that the SED device wakes up exactly at every poll period, set the following Kconfig options to the value greater than the poll period value (for Matter ICD :kconfig:option:`CONFIG_CHIP_ICD_SLOW_POLL_INTERVAL`):
+
+* :kconfig:option:`CONFIG_OPENTHREAD_MLE_CHILD_TIMEOUT`
+* :kconfig:option:`CONFIG_OPENTHREAD_CHILD_SUPERVISION_CHECK_TIMEOUT`
+* :kconfig:option:`CONFIG_OPENTHREAD_CHILD_SUPERVISION_INTERVAL`
+
 Matter over Wi-Fi
 =================
 
diff --git a/doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst b/doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst
index 9d97718ef55a..1832fb2f965d 100644
--- a/doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst
+++ b/doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst
@@ -154,7 +154,7 @@ nRF IEEE 802.15.4 radio driver
 Thread
 ------
 
-|no_changes_yet_note|
+* Added Kconfig options for configuring the MLE child update timeout, child supervision interval, and child supervision check timeout.
 
 Zigbee
 ------
diff --git a/west.yml b/west.yml
index f4d77eb929e2..3c3217b7e620 100644
--- a/west.yml
+++ b/west.yml
@@ -69,7 +69,7 @@ manifest:
     # https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/guides/modules.html
     - name: zephyr
       repo-path: sdk-zephyr
-      revision: c19304355a55e512d13cde72a177f98ec684d928
+      revision: pull/2308/head
       import:
         # In addition to the zephyr repository itself, NCS also
         # imports the contents of zephyr/west.yml at the above