Skip to main content
cve.nowby Sazabi
← All vulnerabilities
CVE-2025-38298

EDAC/skx_common: Fix general protection fault

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 5.4.295, 5.10.239, 5.15.186, 6.1.142, 6.6.94, and 1 more
None on Exploit-DB, Metasploit or GitHub

Summary

In the Linux kernel, the following vulnerability has been resolved: EDAC/skx_common: Fix general protection fault After loading i10nm_edac (which automatically loads skx_edac_common), if unload only i10nm_edac, 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 mce_gen_pool_process RIP: 0010:string+0x53/0xe0 ... Call Trace: <TASK> ? die_addr+0x37/0x90 ? exc_general_protection+0x1e7/0x3f0 ? asm_exc_general_protection+0x26/0x30 ? string+0x53/0xe0 vsnprintf+0x23e/0x4c0 snprintf+0x4d/0x70 skx_adxl_decode+0x16a/0x330 [skx_edac_common] skx_mce_check_error.part.0+0xf8/0x220 [skx_edac_common] skx_mce_check_error+0x17/0x20 [skx_edac_common] ... The issue arose was because the variable 'adxl_component_count' (inside skx_edac_common), which counts the ADXL components, was not reset. During the reloading of i10nm_edac, 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 'adxl_component_count' in adxl_put(), which is called during the unloading of {skx,i10nm}_edac.

Timeline

  1. CVE published
  2. Record last updated

Affected versions

  • Linux Linux

    From 5.4.282 · fixed in 5.4.295; From 5.10.224 · fixed in 5.10.239; From 5.15.165 · fixed in 5.15.186; From 6.1.103 · fixed in 6.1.142; From 6.6.44 · fixed in 6.6.94; From 6.10.3 · fixed in 6.11

  • Linux Linux

    6.11

References 8

git.kernel.org