CVE-2025-38367

High

In the Linux kernel, the following vulnerability has been resolved: LoongArch: KVM: Avoid overflow with array index The variable index is modified and reused as array index when modify register EIOINTC_ENABLE. There will be array index overflow problem.

Package Linux Kernel
Published 2025-07-25
Last modified 2025-11-19
CVSS version 3.1
Patch available
Yes

CVSS 3.1 score

7.8

out of 10
High
Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High
Vector string
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Weakness type

CWE-129

CVE-2025-38367 is classified as CWE-129

See CWE-129 on MITRE CWE for full details on this weakness type.

Affected versions

Linux kernel versions 6.13 and later are affected. Fixed in 6.15.5, 6.16 and their respective stable series.

Affected from
≥ 6.13
Fixed in
✓ 6.15.5 6.15.x ✓ 6.16

References

The following references provide additional information about CVE-2025-38367 including vendor advisories, patch commits, exploit details, and third-party analysis. Links are sourced from the NIST NVD database.

Frequently asked questions

  • What is CVE-2025-38367?

    CVE-2025-38367 is a High severity Linux kernel vulnerability with a CVSS score of 7.8 out of 10 . It affects Linux kernel versions from 6.13 onward and has been patched in 6.15.5 and 6.16. CVE-2025-38367 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

  • What is the CVSS score for CVE-2025-38367?

    CVE-2025-38367 has a CVSS score of 7.8 out of 10, rated High severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H .

  • Is there a patch available for CVE-2025-38367?

    Yes — CVE-2025-38367 has been patched. Fixed versions include 6.15.5 and 6.16. If you are running Linux kernel 6.13 or later up to the fix versions, apply the relevant patch for your kernel branch.

  • Is CVE-2025-38367 actively exploited?

    No — CVE-2025-38367 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.