In the Linux kernel, the following vulnerability has been resolved: EDAC/skxcommon: Fix general protection fault After loading i10nmedac (which automatically loads skxedaccommon), if unload only i10nmedac, then reload it and perform error injection testing, a general protection fault may occur: mce: [Hardware Error]: Machine check events logged Oops: general protection fault ... ... Workqueue: events mcegenpoolprocess RIP: 0010:string+0x53/0xe0 ... Call Trace: <TASK> ? dieaddr+0x37/0x90 ? excgeneralprotection+0x1e7/0x3f0 ? asmexcgeneralprotection+0x26/0x30 ? string+0x53/0xe0 vsnprintf+0x23e/0x4c0 snprintf+0x4d/0x70 skxadxldecode+0x16a/0x330 [skxedaccommon] skxmcecheckerror.part.0+0xf8/0x220 [skxedaccommon] skxmcecheckerror+0x17/0x20 [skxedaccommon] ... The issue arose was because the variable 'adxlcomponentcount' (inside skxedaccommon), which counts the ADXL components, was not reset. During the reloading of i10nmedac, the count was incremented by the actual number of ADXL components again, resulting in a count that was double the real number of ADXL components. This led to an out-of-bounds reference to the ADXL component array, causing the general protection fault above. Fix this issue by resetting the 'adxlcomponentcount' in adxlput(), which is called during the unloading of {skx,i10nm}_edac.