Bluetooth controller lifecycle status



A Bluetooth controller, when it is at the end or has already finished its product life cycle, will not receive updates from the manufacturer, meaning that the identification of vulnerabilities in its firmware or any other component will make the vulnerability permanent in the device and there will not be an official way to fix it.

Therefore, it is important to check at what point in the lifecycle the Bluetooth controller is, as this can indicate whether it will be necessary to replace the device in the short, medium, or long term.


After identifying the Bluetooth controller, it will be necessary to consult the manufacturer’s documentation to find out at which point in the life cycle it is.

You can find a list of controllers that have already reached an end of support status in the End of life Bluetooth controllers annex. Alternatively, if the device is not listed, it will be necessary to consult the manufacturer’s website, different supplier websites, or various search engines. In addition to common search engines and the manufacturer’s page, searches are recommended on the following providers/manufacturers:

The resources that can be useful for the identification of the controller model in the device can be found in the following table:

ID Description
BSAM-RES-01 Physical identification of the controller
BSAM-RES-02 Identify controller through reports


Upon disassembly of a Bluetooth device (BSAM-RES-01 (Physical identification of the controller)) an nRF51822 controller is identified. A search in Mouser’s website indicates that this controller is not recommended for new designs because the manufacturer has issued this recommendation for having reached the end of its lifecycle and there are products that replace it.

The Mouser provider indicating that the controller is not recommended for new designs

The manufacturer also lists an informational note on their website about a vulnerability affecting all nRF51 family devices. Had the device been out of support at the time, the vulnerability would not have been patched, leaving the customer exposed.

This is important because it is possible that the controller will not be supported for fixes affecting security in a timeframe shorter than the support to be given to the device under study.