Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2025-38298

7.8 · HIGH

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 o…

Published Jul 10, 2025CWE-787EPSS 0.23%

Overview

CVE-2025-38298 is a high-severity vulnerability. It was published on July 10, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

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_

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/20d2d476b3ae18041be423671a8637ed5ffd6958Refgit.kernel.org/stable/c/31ef6f7c9aee3be78d63789653e92350f2537f93Refgit.kernel.org/stable/c/3f5d0659000923735350da60ad710f8c804544feRefgit.kernel.org/stable/c/80bf28fd623d97dd4f4825fbbe9d736cec2afba3Refgit.kernel.org/stable/c/a13e8343ffcff27af1ff79597ff7ba241e6d9471Refgit.kernel.org/stable/c/a6ed3a6edff09c1187cc6ade7f5967bca2376a13Refgit.kernel.org/stable/c/bf6a8502a5f4ff6e4d135d795945cdade49ec8b0Refgit.kernel.org/stable/c/e8530ed3c0769a4d8f79c212715ec1cf277787f8Reflists.debian.org/debian-lts-announce/2025/10/msg00007.htmlReflists.debian.org/debian-lts-announce/2025/10/msg00008.html

How CyberStrike helps

Frequently asked questions

What is CVE-2025-38298?

CVE-2025-38298 is a high-severity vulnerability. It was published on July 10, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2025-38298?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2025-38298?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-38298?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-38298 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2025

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999