NCS Mesh: Division by 0 if CTL Temperature Range matches

RE: NCS Mesh: Division by 0 if CTL Temperature Range matches

Joakim Jakobsen — Thu, 17 Aug 2023 11:20:26 GMT

Hi again.

I'm so this was delayed for so long.

If you take a look at: https://github.com/nrfconnect/sdk-nrf/blob/main/subsys/bluetooth/mesh/light_ctl_internal.h
you can see changes to the temp_to_lvl function.

Br,
Joakim

RE: NCS Mesh: Division by 0 if CTL Temperature Range matches

mesh777 — Wed, 21 Jun 2023 08:18:33 GMT

Hi Joakim. Is there any news upon this case? It is almost two months since I reported the problem.

RE: NCS Mesh: Division by 0 if CTL Temperature Range matches

mesh777 — Tue, 13 Jun 2023 07:26:10 GMT

This issue leads to system vulnerability, if somebody sets ranges to the same value, device crashes on boot all the time as values are saved persistently. Therefore we expect it to be fixed as soon as possible.

RE: NCS Mesh: Division by 0 if CTL Temperature Range matches

mesh777 — Mon, 05 Jun 2023 11:02:59 GMT

I have not checked if crash persists on 2.3.0 and 2.4.0, but function where crash was observed (temp_to_lvl) on 2.2.0 is not changed on the latest source code too.

https://github.com/nrfconnect/sdk-nrf/blob/main/subsys/bluetooth/mesh/light_ctl_internal.h

RE: NCS Mesh: Division by 0 if CTL Temperature Range matches

Joakim Jakobsen — Mon, 05 Jun 2023 10:12:38 GMT

I haven't heard anything.

I can check if we have a timeline for a potential fix, or if we have something we can share.

Did you check if there was any changes in the latest version of NCS (2.4.0)?

Br,
Joakim

RE: NCS Mesh: Division by 0 if CTL Temperature Range matches

mesh777 — Thu, 01 Jun 2023 08:20:45 GMT

Is there any response upon this issue?

Maybe you could propose a quick fix for it.

RE: NCS Mesh: Division by 0 if CTL Temperature Range matches

Joakim Jakobsen — Fri, 28 Apr 2023 13:03:10 GMT

Hi.

Thank you for your report. I'll take a closer look and report it to our developers.

Br,
Joakim