NVD / CVE Program· CNA Linux

CVE-2025-38346: ftrace: Fix UAF when lookup kallsym after ftrace disabled

Noroxi assessment

Priority: Monitor (action score 31/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Linux Linux 03a162933c4a03b9f1a84f7d8482903c7e1e11bb, 6805582abb720681dd1c87ff677f155dcf4e86c9, 83a692a9792aa86249d68a8ac0b9d55ecdd255fa; azl3 kernel 6.6.92.2-2 on Azure Linux 3.0 6.6.96.1-1.

Low priority for now. Upgrade to Linux Linux 03a162933c4a03b9f1a84f7d8482903c7e1e11bb, 6805582abb720681dd1c87ff677f155dcf4e86c9, 83a692a9792aa86249d68a8ac0b9d55ecdd255fa; azl3 kernel 6.6.92.2-2 on Azure Linux 3.0 6.6.96.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: ftrace: Fix UAF when lookup kallsym after ftrace disabled The following issue happens with a buggy module: BUG: unable to handle page fault for address: ffffffffc05d0218 PGD 1bd66f067 P4D 1bd66f067 PUD 1bd671067 PMD 101808067 PTE 0 Oops: Oops: 0000 [#1] SMP KASAN PTI Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS RIP: 0010:sized_strscpy+0x81/0x2f0 RSP: 0018:ffff88812d76fa08 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffffffffc0601010 RCX: dffffc0000000000 RDX: 0000000000000038 RSI: dffffc0000000000 RDI: ffff88812608da2d RBP: 8080808080808080 R08: ffff88812608da2d R09: ffff88812608da68 R10: ffff88812608d82d R11: ffff88812608d810 R12: 0000000000000038 R13: ffff88812608da2d R14: ffffffffc05d0218 R15: fefefefefefefeff FS: 00007fef552de740(0000) GS:ffff8884251c7000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffffffc05d0218 CR3: 00000001146f0000 CR4: 00000000000006f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> ftrace_mod_get_kallsym+0x1ac/0x590 update_iter_mod+0x239/0x5b0 s_next+0x5b/0xa0 seq_read_iter+0x8c9/0x1070 seq_read+0x249/0x3b0 proc_reg_read+0x1b0/0x280 vfs_read+0x17f/0x920 ksys_read+0xf3/0x1c0 do_syscall_64+0x5f/0x2e0 entry_SYSCALL_64_after_hwframe+0x76/0x7e The above issue may happen as follows: (1) Add kprobe tracepoint; (2) insmod test.ko; (3) Module triggers ftrace disabled; (4) rmmod test.ko; (5) cat /proc/kallsyms; --> Will trigger UAF as test.ko already removed; ftrace_mod_get_kallsym() ... strscpy(module_name, mod_map->mod->name, MODULE_NAME_LEN); ... The problem is when a module triggers an issue with ftrace and sets ftrace_disable. The ftrace_disable is set when an anomaly is discovered and to prevent any more damage, ftrace stops all text modification. The issue that happened was that the ftrace_disable stops more than just the text modification. When a module is loaded, its init functions can also be traced. Because kallsyms deletes the init functions after a module has loaded, ftrace saves them when the module is loaded and function tracing is enabled. This allows the output of the function trace to show the init function names instead of just their raw memory addresses. When a module is removed, ftrace_release_mod() is called, and if ftrace_disable is set, it just returns without doing anything more. The problem here is that it leaves the mod_list still around and if kallsyms is called, it will call into this code and access the module memory that has already been freed as it will return: strscpy(module_name, mod_map->mod->name, MODULE_NAME_LEN); Where the "mod" no longer exists and triggers a UAF bug.

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

Published: Jul 10, 2025
Updated: Oct 15, 2026
EPSS: 0.2% · 10th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 7.8
CNA · Linux: 7.8; agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_kernel
debian	debian linux	cpe:2.3:o:debian:debian_linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

debian debian linux11.0
linux linux kernel5.5 and later · before 5.10.239
linux linux kernel5.11 and later · before 5.15.186
linux linux kernel5.16 and later · before 6.1.142
linux linux kernel4.15 and later · before 5.4.295
linux linux kernel6.7 and later · before 6.12.35
linux linux kernel6.13 and later · before 6.15.4
linux linux kernel6.2 and later · before 6.6.95

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

Linux Linux
- 4.15affected
- aba4b5c22cbac296f4081a0476d0c55828f135b4 and later · before d064c68781c19f378af1ae741d9132d35d24b2bbaffected · git
- aba4b5c22cbac296f4081a0476d0c55828f135b4 and later · before 8690cd3258455bbae64f809e1d3ee0f043661c71affected · git
- aba4b5c22cbac296f4081a0476d0c55828f135b4 and later · before 6805582abb720681dd1c87ff677f155dcf4e86c9affected · git
- aba4b5c22cbac296f4081a0476d0c55828f135b4 and later · before 03a162933c4a03b9f1a84f7d8482903c7e1e11bbaffected · git
- aba4b5c22cbac296f4081a0476d0c55828f135b4 and later · before 83a692a9792aa86249d68a8ac0b9d55ecdd255faaffected · git
- aba4b5c22cbac296f4081a0476d0c55828f135b4 and later · before 8e89c17dc8970c5f71a3a991f5724d4c8de42d8caffected · git
- aba4b5c22cbac296f4081a0476d0c55828f135b4 and later · before f78a786ad9a5443a29eef4dae60cde85b7375129affected · git
- aba4b5c22cbac296f4081a0476d0c55828f135b4 and later · before f914b52c379c12288b7623bb814d0508dbe7481daffected · git
- before 4.15not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
AlmaLinux:10	kernel	before 6.12.0-211.7.1.el10_2	6.12.0-211.7.1.el10_2
AlmaLinux:10	kernel-64k	before 6.12.0-211.7.1.el10_2	6.12.0-211.7.1.el10_2
AlmaLinux:10	kernel-64k-core	before 6.12.0-211.7.1.el10_2	6.12.0-211.7.1.el10_2
AlmaLinux:10	kernel-64k-debug	before 6.12.0-211.7.1.el10_2	6.12.0-211.7.1.el10_2
AlmaLinux:10	kernel-64k-debug-core	before 6.12.0-211.7.1.el10_2	6.12.0-211.7.1.el10_2
AlmaLinux:10	kernel-64k-debug-devel	before 6.12.0-211.7.1.el10_2	6.12.0-211.7.1.el10_2
AlmaLinux:10	kernel-64k-debug-devel-matched	before 6.12.0-211.7.1.el10_2	6.12.0-211.7.1.el10_2
AlmaLinux:10	kernel-64k-debug-modules	before 6.12.0-211.7.1.el10_2	6.12.0-211.7.1.el10_2
AlmaLinux:10	kernel-64k-debug-modules-core	before 6.12.0-211.7.1.el10_2	6.12.0-211.7.1.el10_2
AlmaLinux:10	kernel-64k-debug-modules-extra	before 6.12.0-211.7.1.el10_2	6.12.0-211.7.1.el10_2
AlmaLinux:10	kernel-64k-devel	before 6.12.0-211.7.1.el10_2	6.12.0-211.7.1.el10_2
AlmaLinux:10	kernel-64k-devel-matched	before 6.12.0-211.7.1.el10_2	6.12.0-211.7.1.el10_2
AlmaLinux:10	kernel-64k-modules	before 6.12.0-211.7.1.el10_2	6.12.0-211.7.1.el10_2
AlmaLinux:10	kernel-64k-modules-core	before 6.12.0-211.7.1.el10_2	6.12.0-211.7.1.el10_2
AlmaLinux:10	kernel-64k-modules-extra	before 6.12.0-211.7.1.el10_2	6.12.0-211.7.1.el10_2
AlmaLinux:10	kernel-abi-stablelists	before 6.12.0-211.7.1.el10_2	6.12.0-211.7.1.el10_2
AlmaLinux:10	kernel-core	before 6.12.0-211.7.1.el10_2	6.12.0-211.7.1.el10_2
AlmaLinux:10	kernel-cross-headers	before 6.12.0-211.7.1.el10_2	6.12.0-211.7.1.el10_2
AlmaLinux:10	kernel-debug	before 6.12.0-211.7.1.el10_2	6.12.0-211.7.1.el10_2
AlmaLinux:10	kernel-debug-core	before 6.12.0-211.7.1.el10_2	6.12.0-211.7.1.el10_2
AlmaLinux:10	kernel-debug-devel	before 6.12.0-211.7.1.el10_2	6.12.0-211.7.1.el10_2
AlmaLinux:10	kernel-debug-devel-matched	before 6.12.0-211.7.1.el10_2	6.12.0-211.7.1.el10_2
AlmaLinux:10	kernel-debug-modules	before 6.12.0-211.7.1.el10_2	6.12.0-211.7.1.el10_2
AlmaLinux:10	kernel-debug-modules-core	before 6.12.0-211.7.1.el10_2	6.12.0-211.7.1.el10_2

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now

Published before and after this one in the same product

← EarlierCVE-2025-38344Jul 10, 2025 · ACPICA: fix acpi parse and parseext cache leaks
22Monitor
← EarlierCVE-2025-38345Jul 10, 2025 · ACPICA: fix acpi operand cache leak in dswstate.c
22Monitor
Later →CVE-2025-38349Jul 18, 2025 · eventpoll: don't decrement ep refcount while still holding the ep mutex
31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Linux Linux	03a162933c4a03b9f1a84f7d8482903c7e1e11bb	Vendor (CNA)
Linux Linux	6805582abb720681dd1c87ff677f155dcf4e86c9	Vendor (CNA)
Linux Linux	83a692a9792aa86249d68a8ac0b9d55ecdd255fa	Vendor (CNA)
Linux Linux	8690cd3258455bbae64f809e1d3ee0f043661c71	Vendor (CNA)
Linux Linux	8e89c17dc8970c5f71a3a991f5724d4c8de42d8c	Vendor (CNA)
Linux Linux	d064c68781c19f378af1ae741d9132d35d24b2bb	Vendor (CNA)
Linux Linux	f78a786ad9a5443a29eef4dae60cde85b7375129	Vendor (CNA)
Linux Linux	f914b52c379c12288b7623bb814d0508dbe7481d	Vendor (CNA)
azl3 kernel 6.6.92.2-2 on Azure Linux 3.0	6.6.96.1-1 · CBL-Mariner Releases	Microsoft (MSRC)
almalinux:kernel	6.12.0-211.7.1.el10_2 · AlmaLinux:10	Package registry (OSV)
almalinux:kernel-64k	6.12.0-211.7.1.el10_2 · AlmaLinux:10	Package registry (OSV)
almalinux:kernel-64k-core	6.12.0-211.7.1.el10_2 · AlmaLinux:10	Package registry (OSV)
almalinux:kernel-64k-debug	6.12.0-211.7.1.el10_2 · AlmaLinux:10	Package registry (OSV)
almalinux:kernel-64k-debug-core	6.12.0-211.7.1.el10_2 · AlmaLinux:10	Package registry (OSV)
almalinux:kernel-64k-debug-devel	6.12.0-211.7.1.el10_2 · AlmaLinux:10	Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched	6.12.0-211.7.1.el10_2 · AlmaLinux:10	Package registry (OSV)
almalinux:kernel-64k-debug-modules	6.12.0-211.7.1.el10_2 · AlmaLinux:10	Package registry (OSV)
almalinux:kernel-64k-debug-modules-core	6.12.0-211.7.1.el10_2 · AlmaLinux:10	Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra	6.12.0-211.7.1.el10_2 · AlmaLinux:10	Package registry (OSV)
almalinux:kernel-64k-devel	6.12.0-211.7.1.el10_2 · AlmaLinux:10	Package registry (OSV)
almalinux:kernel-64k-devel-matched	6.12.0-211.7.1.el10_2 · AlmaLinux:10	Package registry (OSV)
debian:linux	6.1.147-1 · Debian:12	Package registry (OSV)
red hat:kernel-64k-debug-debuginfo	0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2	Package registry (OSV)
red hat:kernel-64k-debug-devel	0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2	Package registry (OSV)
red hat:kernel-64k-debug-devel-matched	0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2	Package registry (OSV)
red hat:kernel-64k-debuginfo	0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2	Package registry (OSV)
red hat:kernel-64k-devel	0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2	Package registry (OSV)
red hat:kernel-64k-devel-matched	0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2	Package registry (OSV)
red hat:kernel-debug-debuginfo	0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2	Package registry (OSV)
red hat:kernel-debug-devel	0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

SSVC exploitation— → noneOct 15, 2026, 11:07 PM UTC
Fix✗ → ✓Sep 28, 2026, 10:08 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/03a162933c4a03b9f1a84f7d8482903c7e1e11bb

Show all references (9 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records