Yes, this certainly looks like it could be related to bug #1274376, which is a kernel oops in the efivarfs code.
Yes, this certainly looks like it could be related to bug #1274376, which is a kernel oops in the efivarfs code.