CVE-2025-38298

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