This is fixed in Oracular with 5.77-0ubuntu2. The aforementioned GitHub issue is a duplicate of another. That issue is mentioned directly in the patch included with this latest version in Ubuntu. It even explains the source of the issue— a change in the kernel:
From 366a8c522b648f47147de4852c5c030d69b916b3 Mon Sep 17 00:00:00 2001
From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: Wed, 28 Aug 2024 11:30:16 -0400
Subject: [PATCH] adapter: Fix up address type when loading keys
Due to kernel change 59b047bc9808
("Bluetooth: MGMT/SMP: Fix address type when using SMP over BREDR/LE")
some keys maybe store using the wrong/invalid address type as per MGMT
API, so this attempts to fix them up.
Fixes: https://github.com/bluez/bluez/issues/875
---
src/adapter.c | 20 ++++++++++++++++++--
1 file changed, 18 insertions(+), 2 deletions(-)
Interestingly, the kernel commit mentioned, found in 6.7-rc7, was authored by a bluez contributor. Looks like the commit was reverted in 6.11-rc7. So it seems Plucky (on 6.12.0-12.12 as I type) doesn’t even need the change.
Looking at the rest of the bug report, it’s been confirmed for Noble but unassigned to anyone. I’m not sure I think SRUs are necessarily good first tasks for new packagers, but fixing it for Noble sure is. You’re essentially just copying the above on a different version, making sure it builds, and testing it. I’m sure someone would help sponsor and maybe even do the requisite paperwork.