Comment 41 for bug 1956461

Technically this fix hasn't actually landed in an official kernel yet. Right now they are in the part of the cycle where they release weekly release candidate builds of 5.17. This fix first showed up in v5.17-rc3. I would expect v5.17-rc6 to be released today, and the final 5.17 to be released in (early?) March.

I'm not an expert at Ubuntu's release processes, but I went through a similar wait on a different bug fix. Here is my understanding of the process of this fix getting into Ubuntu's 5.4 kernel:

The patch was CC'd to linux-stable. I would expect it to be accepted as a stable patch, because it fixes a regression. It doesn't appear to have been accepted yet. Once it is accepted as a stable patch, it should show up in this tree: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/?h=linux-5.4.y

Then, a new 5.4.x stable mainline kernel will be released containing it. Sometime after that, Ubuntu should automatically pick up the patch into their kernel. I'm not sure if there's a way to speed up the process to get them to cherry-pick just this fix sooner. It is a seriously annoying regression!