A kernel-based workaround for the underlying issue has now landed in all currently supported linux-stable branches:
linux-6.8: 6.8-rc7 (f45812cc23fb74bef62d4eb8a69fe7218f4b9f2a) linux-6.7: 6.7.9 (cbf12e716a52d260fabecdca7d5f6e7cd07aed6c) linux-6.6: 6.6.21 (71da10e633a96593cf59af3f322a9c49a22cb71e) linux-6.1: 6.1.81 (249d6ca4ff0022a4b51a8eb9fac6d7bff2c94d1b) linux-5.15: 5.15.154 (9bc9c11c151ab27214cc204d954ee902e9bbe8e2) linux-5.10: 5.10.215 (f33255ccbb0f627da76364cce72cf980d027142c) linux-5.4: 5.4.274 (34b5d2ff9ed5cdea9f971f394c0d623761a4d357) linux-4.19: 4.19.312 (a7bd7dbaa2ddcf8c5ed5d96df240f1442447d252) Unfortunately, said kernel has to be used during installation, so the issue won't be fixed in practice until the next set of installation images are built. Afterwards, this issue can probably be considered "fixed", at least with regards to the Fujitsu Lifebook AH532 (and extended family). The other bug report for the Dell Latitude 5510 seems to be unrelated.
