BlueZ Bluetooth Mesh crypto kernel modules missing, bluetooth adapters without public address cannot be initialized.

[zalatnaicsongor]

Describe the issue you are experiencing

Some bluetooth HCI adapters, such as NRF52 based ones cannot be initialized due to the lack of the following kernel modules:

	CONFIG_CRYPTO_USER
	CONFIG_CRYPTO_USER_API
	CONFIG_CRYPTO_USER_API_AEAD
	CONFIG_CRYPTO_USER_API_HASH
	CONFIG_CRYPTO_USER_API_SKCIPHER

	CONFIG_CRYPTO_AES
	CONFIG_CRYPTO_CCM
	CONFIG_CRYPTO_AEAD
	CONFIG_CRYPTO_CMAC

See: https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/README#n64

What operating system image do you use?

ova (for Virtual Machines)

What version of Home Assistant Operating System is installed?

12.2

Did you upgrade the Operating System.

Yes

Steps to reproduce the issue

Attach a bluetooth controller such as an NRF52 based one (https://docs.zephyrproject.org/latest/samples/bluetooth/hci_usb/README.html) and you'll observe the following output:

Apr 22 00:13:59 homeassistant bluetoothd[2085427]: src/adapter.c:get_static_addr() Unable t
Apr 22 00:13:59 homeassistant bluetoothd[2085427]: src/adapter.c:get_static_addr() Failed t
Apr 22 00:13:59 homeassistant bluetoothd[2085427]: No Bluetooth address for index 0

Anything in the Supervisor logs that might be useful for us?

-

Anything in the Host logs that might be useful for us?

-

System information

No response

Additional information

See: raspberrypi/linux#3628