Intel Wifi AX1690i: iwlwifi Firmware error, connection drops

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu

Description: Ubuntu 22.10
Release: 22.10

2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center

linux-image-5.19.0-26-generic:
  Installiert: 5.19.0-26.27
  Installationskandidat: 5.19.0-26.27
  Versionstabelle:
 *** 5.19.0-26.27 500
        500 http://de.archive.ubuntu.com/ubuntu kinetic-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu kinetic-security/main amd64 Packages
        100 /var/lib/dpkg/status

linux-image-unsigned-6.0.9-060009-generic:
  Installiert: 6.0.9-060009.202211161102
  Installationskandidat: 6.0.9-060009.202211161102
  Versionstabelle:
 *** 6.0.9-060009.202211161102 100
        100 /var/lib/dpkg/status

3) What you expected to happen

Wifi should work.

4) What happened instead

Wifi connects to the AP, but it is hit or miss if IPv6 routing will work or not. If IPv6 does not work, IPv6 addresses are pingable in the local LAN, but not to the internet.
Also Wifi is dropping out sometimes and is not able to authenticate to the AP anymore.
I will attach 2 dmesg files, one with a complete dropout of the connection and one with a firmware microcode error.

Addresses and routes seem to be acquired correctly.

wlo1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
        inet 192.168.0.214 netmask 255.255.255.0 broadcast 192.168.0.255
        inet6 fd00::3bb3:fba0:b3fc:20dd prefixlen 64 scopeid 0x0<global>
        inet6 2003:f8:5f13:800:654:b62:4a02:83b3 prefixlen 64 scopeid 0x0<global>
        inet6 2003:f8:5f13:800:81a8:9901:7bb0:1db9 prefixlen 64 scopeid 0x0<global>
        inet6 fd00::6d0f:43c:c1a1:dd7e prefixlen 64 scopeid 0x0<global>
        inet6 fe80::21c5:41c1:6a36:9afb prefixlen 64 scopeid 0x20<link>
        ether 4c:44:5b:dc:06:63 txqueuelen 1000 (Ethernet)
        RX packets 8194603 bytes 8936242173 (8.9 GB)
        RX errors 0 dropped 23213 overruns 0 frame 0
        TX packets 3238917 bytes 1313064667 (1.3 GB)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

Destination Next Hop Flag Met Ref Use If
p200300f85f1308000000000000000000.dip0.t-ipconnect.de/64 [::] U 600 2 0 wlo1
p200300f85f1308000000000000000000.dip0.t-ipconnect.de/56 fe80::9a9b:cbff:fe96:7716 UG 600 1 0 wlo1
fd00::/64 [::] U 600 1 0 wlo1
fe80::/64 [::] U 1024 2 0 wlo1
[::]/0 fe80::dea6:32ff:fe39:32d1 UG 600 21 0 wlo1
[::]/0 fe80::9a9b:cbff:fe96:7716 UG 600 20 0 wlo1
ip6-localhost/128 [::] Un 0 3 0 lo
p200300f85f13080006540b624a0283b3.dip0.t-ipconnect.de/128 [::] Un 0 14 0 wlo1
p200300f85f13080081a899017bb01db9.dip0.t-ipconnect.de/128 [::] Un 0 3 0 wlo1
fd00::3bb3:fba0:b3fc:20dd/128 [::] Un 0 2 0 wlo1
fd00::6d0f:43c:c1a1:dd7e/128 [::] Un 0 3 0 wlo1
fe80::21c5:41c1:6a36:9afb/128 [::] Un 0 9 0 wlo1
ip6-mcastprefix/8 [::] U 256 3 0 wg0
ip6-mcastprefix/8 [::] U 256 19 0 wlo1
[::]/0 [::] !n -1 1 0 lo

Any other devices on the network do not have this issue. I have two devices using this driver having similar issues.