The requirement to reboot is documented, and it’s an order of magnitude away from being a regular problem - ie. 51 days instead of every 51 minutes.

This puts it in the same maintenance bucket as parts that need regular replacement.

To use the “part needing regular replacement” analogy - the bug could be fixed for an extra $Y. But everything in engineering is a trade off. Choosing not to fix the bug might bring costs down to something competitive with the market.

Plus, like any part that could be made more reliable for extra cost, there might be no benefit due to service schedules. Say you could design a part that is 60% worn at service time vs a cheaper part that’s 90% worn - it they will both need replacing at the same time, you’d go for the lower cost design.

Eg. if some service task requires resetting the avionics every 40 days, that’s less than 51 days so there may as well be no bug.