Comment 3 for bug 1797367

The stack trace looks to indicate a debugfs read triggering an out of bounds read against a kernel object backed by the slab. That is that the read is offset into the object such that the attempted read would have traversed onto the following object exposing kernel memory for an unrelated item. Do we know what the userspace application triggering this is actually doing when the fault triggers?