CVE-2025-37845: tracing: fprobe events: Fix possible UAF on modules
In the Linux kernel, the following vulnerability has been resolved:
tracing: fprobe events: Fix possible UAF on modules
Commit ac91052f0ae5 ("tracing: tprobe-events: Fix leakage of module
refcount") moved try_module_get() from __find_tracepoint_module_cb()
to find_tracepoint() caller, but that introduced a possible UAF
because the module can be unloaded before try_module_get(). In this
case, the module object should be freed too. Thus, try_module_get()
does not only fail but may access to the freed object.
To avoid that, try_module_get() in __find_tracepoint_module_cb()
again.
Security readout for executives and security teams
Plain-English summary
A Linux kernel tracing flaw can use a module object after it has been freed during module unloading. A local, low-privileged attacker may be able to trigger memory corruption, potentially compromising confidentiality, integrity, or availability. The supplied CVSS score is 7.8 (High).
Executive priority
Treat as a high-priority kernel maintenance issue, especially on multi-user or otherwise locally accessible Linux systems. Patch through supported distribution channels after compatibility testing. Escalate systems permitting untrusted local access, while recognizing that the supplied evidence does not establish active exploitation.
Technical view
A refcount change moved try_module_get() out of __find_tracepoint_module_cb(), creating a race between locating a tracepoint module and acquiring its reference. If unloading occurs between those operations, try_module_get() may access the freed module object. The documented correction restores reference acquisition inside the callback.
Likely exposure
Exposure requires an affected Linux kernel and local low-privileged access, according to the supplied CVSS vector. Systems using relevant fprobe tracing and unloadable modules warrant priority. The supplied affected-version metadata is ambiguous, so distribution package versions must be mapped to the referenced stable fixes.
Exploitation context
The CVSS vector indicates local attack, low complexity, low privileges, no user interaction, and potentially high confidentiality, integrity, and availability impact. The bundle marks this CVE as absent from KEV and provides no evidence of active exploitation or a public exploit.
Researcher notes
This is a race-driven use-after-free in fprobe event tracepoint module discovery. The vulnerable ordering permits module unloading before reference acquisition. No CWE is assigned in the bundle. Exact vulnerable release boundaries should not be inferred from the supplied version arrays; validate ancestry or backports against the referenced commits.
Mitigation direction
Install a vendor or distribution kernel containing the applicable referenced stable fix.
Confirm whether distribution kernels backport the fix despite retaining older version numbers.
Reboot affected systems into the corrected kernel after installation.
Until patched, reduce unnecessary local account access and consult vendor guidance for supported mitigations.
Validation and detection
Inventory running kernel and distribution package versions across Linux systems.
Map each packaged kernel to the four referenced upstream stable commits or vendor advisories.
Verify the corrected kernel is installed and currently running after reboot.
Review whether relevant tracing facilities and unloadable modules are available on exposed systems.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-37845 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
5Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.