Searched refs:risk (Results 1 – 25 of 26) sorted by relevance
12
| /Zephyr-latest/soc/nordic/nrf53/ |
| D | CMakeLists.txt | 17 At your own risk, you can suppress this warning by setting
|
| /Zephyr-latest/modules/hal_nordic/nrfs/ |
| D | CMakeLists.txt | 39 …r Nordic Semiconductor INTERNAL purposes ONLY. Use it with caution due to risk of hardware damage!…
|
| /Zephyr-latest/tests/subsys/edac/ibecc/ |
| D | README.rst | 37 Due to high security risk Error Injection capability should not be
|
| /Zephyr-latest/subsys/usb/device/class/dfu/ |
| D | Kconfig | 46 Be aware that upload capability can be a security risk because
|
| /Zephyr-latest/drivers/ethernet/ |
| D | Kconfig.dwmac | 65 memory. A smaller number increases the risk of an overflow and
|
| /Zephyr-latest/subsys/net/l2/ppp/ |
| D | Kconfig | 107 execution to the lower layer network stack, with a high risk of
|
| /Zephyr-latest/doc/hardware/peripherals/edac/ |
| D | ibecc.rst | 44 Due to high security risk Error Injection capability should not be enabled for
|
| /Zephyr-latest/doc/kernel/services/other/ |
| D | atomic.rst | 49 incremented atomically, there is no risk that it will become corrupted
|
| D | fatal.rst | 198 memory protection hardware, there is no risk of data corruption to memory
|
| /Zephyr-latest/doc/security/standards/ |
| D | etsi-303645.rst | 207 risk of automated attacks against a class or type of device.
216 the properties of the technology, risk and usage.
419 shall be unique per device and shall be produced with a mechanism that reduces the risk
468 appropriate to the properties of the technology, risk and usage.
|
| /Zephyr-latest/doc/safety/ |
| D | safety_overview.rst | 65 (SIL) to classify the level of risk reduction required for each safety function. The higher the
66 SIL, the greater the level of risk reduction required.
84 implementation of safety-related systems that aims to reduce the risk of accidents and improve
|
| /Zephyr-latest/drivers/clock_control/ |
| D | Kconfig.nrf | 64 risk.
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | blob_cli.rst | 72 groups. This can lead to longer recovery periods at the end of each block, and increases the risk of
|
| D | core.rst | 60 calling :c:func:`bt_mesh_rpl_pending_store` may reduce a risk of security
|
| /Zephyr-latest/doc/contribute/ |
| D | bin_blobs.rst | 170 Allowing arbitrary library blobs carries a risk of degrading the degree to
175 To mitigate this risk, the scope of upstream library blobs is limited. The
|
| /Zephyr-latest/subsys/net/ip/ |
| D | Kconfig.tcp | 45 execution to the lower layer network stack, with a high risk of
|
| /Zephyr-latest/doc/build/dts/ |
| D | bindings-upstream.rst | 156 There is a risk in using ``default:`` when the value in the binding may be
|
| /Zephyr-latest/doc/develop/test/ |
| D | pytest.rst | 312 risk.
|
| /Zephyr-latest/subsys/debug/ |
| D | Kconfig | 137 GCC is used due to potential risk of a deadlock in libasan.
|
| /Zephyr-latest/doc/services/logging/ |
| D | cs_stm.rst | 36 of data. Circular RAM buffer size is limited to 4k thus there is a risk of data overflow. If
|
| /Zephyr-latest/doc/releases/ |
| D | migration-guide-3.5.rst | 192 last 3 bytes of mac address, resulting in a high risk of collision when using
|
| D | release-notes-3.0.rst | 349 by default. Storing CCC right after it's written reduces risk of
1108 …ooth: host: CCC values are not immediately stored on GATT Server by default (risk of inconsistency)
|
| D | release-notes-1.12.rst | 427 * :github:`6388` - entropy_native_posix doesn't follow "entropy" contract and is thus security risk
|
| /Zephyr-latest/doc/security/ |
| D | vulnerabilities.rst | 1812 arch: riscv: userspace: potential security risk when CONFIG_RISCV_GP=y
|
| /Zephyr-latest/subsys/bluetooth/mesh/ |
| D | Kconfig | 1875 may reduce a risk of security vulnerability and flash wear out.
|
12
