Comment 78 for bug 2044657

@xyv41:
As mentioned in the last comment, the fix is only a cherry-pick so the version will go from 2.1.5-1ubuntu6~22.04.2 to 2.1.5-1ubuntu6~22.04.3 because upgrading to 2.1.14 would bear the risk that other bugs might get fixed, too.

Regarding the release date: for mantic it took about 7 days from verification until release. I don’t know if that's an automated process, but in that case the fix should go out in the next few days.
On the other hand, in post #73 it says that the SRU-Team has been unsubscribed from this bug-report, so maybe they don’t even know that the verification for jammy has been completed and the fix will just get stalled.

Additionally, even when (or if?) the committed package gets released, this only affects the userland tools as well as the dkms-build kernel modules. If you (like 99,9% of all Ubuntu users) use the pre-bundled kernel module, then this also needs an update of the kernel package as well.

To give you an idea: The fix for mantic was committed on February, 2nd and released on the 12th. However, it is still not included in the current kernel package (6.5.0.17.19) nor in the -proposed package (6.5.0.25.25) which is yet to be released. So based on the recent update cycles I suspect it will not reach the end-user until mid of march (for matic!!!).

Therefore, I am expecting that it will be at least one more month (more likely 6 weeks) or so until the jammy fix reaches the end-user. Then we will have a fix found (December, 1st) to fix released time of around 5 months. Quite a good result for a one-line-Hotfix.