Hey there, if I understand correctly this bug which definitely affects linux 4.19.208-1 was closed because it doesn't affect some other version? 5.10.40-1?
I'm asking because (maybe obviously) this bug is affecting my use of 4.19.208-1 in a Kubernetes cluster. I would just pin to 4.19.194-3/4.19.0-17-cloud-amd64 but am mildly concerned about the polkit CVE which, to my understanding, is addressed in 4.19.208-1 but not in 4.19.194-3.
So I guess my question is -- does anyone involved with maintaining the Debian 4.19 image know if there is a fix in sight for this that will eventually be available, maybe for a 4.19.0-19-cloud-amd64 image or something like that? I don't really know how Debian kernel maintenance works. If it would be helpful I could test the latest 4.19 upstream kernel to verify any fixes that might have come through between 4.19.208 and 4.19.227 (the current upstream patch version). I may do it anyway, but it would be encouraging to know if there is some kind of Debian process for getting a new kernel out if my effort succeeds.