CVE-2025-38076

7.8 HIGH 0.2% exploit odds Fix listed Memory safety OS & kernel

What it is

In the Linux kernel, the following vulnerability has been resolved: alloc_tag: allocate percpu counters for module tags dynamically When a module gets unloaded it checks whether any of its tags are still in use and if so, we keep the memory containing module's allocation tags alive until all tags are unused. However percpu counters referenced by the tags are freed by free_module(). This will lead to UAF if the memory allocated by a module is accessed after module was unloaded. To fix this we allocate percpu counters for module allocation tags dynamically and we keep it alive for tags which are still in use after module unloading. This also removes the requirement of a larger PERCPU_MODULE_RESERVE when memory allocation profiling is enabled because percpu memory for counters does not need to be reserved anymore.

At a glance

Exploitability: Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
Exploit odds: 0.2% chance of exploitation in the next 30 days (EPSS).
Fix: A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

2025-06-18 10:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2026-06-17 09:16 UTC Last updatedMost recent change to the record

Why it ranks here

Exploited in the wild: no, CISA does not list it.
Exploit odds: 0.2% in the next 30 days (EPSS).
Severity: 7.8 HIGH (CVSS).
Fix: a patch or advisory is linked.

Details

Published: 2025-06-18 10:15 UTC
Last modified: 2026-06-17 09:16 UTC
Exploit probability: 0.2% · EPSS, next 30 days
Weakness: CWE-416 · Use after free
Record status: Analyzed

Affected

Linux Kernel < 6.14.9
Linux Kernel 6.15

Attack profile CVSS 3.1 · 7.8

Attack vector: Local
Complexity: Low
Privileges needed: Low
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Raw vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2025-38076.md and follow it. Check whether this project is affected by CVE-2025-38076. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

· More options · Status badge

Download Square Reddit

Fix and advisories

References

NVD record · CVE.org record