Likely the bug got introduced in linux-image-5.19.0-42-generic from a mainline kernel newer than 5.19 and no older than 6.2.0.
Likely the bug got introduced in linux-image- 5.19.0- 42-generic from a mainline kernel newer than 5.19 and no older than 6.2.0.