Searched refs:denial (Results 1 – 4 of 4) sorted by relevance
| /Zephyr-latest/doc/security/ |
| D | vulnerabilities.rst | 35 telnet connected user to cause denial of service, and possibly remote
140 denial of service in the best case, or code execution in the worst
168 corruption, resulting in denial of service or possibly code execution
322 uninitialized stack memory. This could result in a crash, denial of
405 be parsed by Zephyr is able to cause a denial of service.
476 would depend on the underlying system call and can range from denial
503 denial of service.
526 Zephyr Bluetooth unchecked packet data results in denial of service
529 failure, or division by zero, resulting in a denial of service attack.
685 infinite loop, resulting in a denial of service attack.
[all …]
|
| D | sensor-threat.rst | 99 time are denial of service (the device rejects valid certificates),
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | overview.rst | 118 - We do not protect against denial of service attacks through thread CPU
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-2.3.rst | 44 resulting in a denial of service.
46 in an assertion failure, or division by zero, resulting in a denial
|
