Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-38106: io_uring: fix use-after-free of sq->thread in __io_uring_show_fdinfo()

HighCVSS 7.8 · v3.1—No exploit Fix available

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.19% (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 ac0b8b327a5677dc6fecdf353d808161525b1ff0, af8c13f9ee040b9a287ba246cf0055f7c77b7cc8, d0932758a0a77b38ba1b39564f3b7aba12407061.

Low priority for now. Upgrade to Linux Linux ac0b8b327a5677dc6fecdf353d808161525b1ff0, af8c13f9ee040b9a287ba246cf0055f7c77b7cc8, d0932758a0a77b38ba1b39564f3b7aba12407061 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: io_uring: fix use-after-free of sq->thread in __io_uring_show_fdinfo() syzbot reports: BUG: KASAN: slab-use-after-free in getrusage+0x1109/0x1a60 Read of size 8 at addr ffff88810de2d2c8 by task a.out/304 CPU: 0 UID: 0 PID: 304 Comm: a.out Not tainted 6.16.0-rc1 #1 PREEMPT(voluntary) Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0x53/0x70 print_report+0xd0/0x670 ? __pfx__raw_spin_lock_irqsave+0x10/0x10 ? getrusage+0x1109/0x1a60 kasan_report+0xce/0x100 ? getrusage+0x1109/0x1a60 getrusage+0x1109/0x1a60 ? __pfx_getrusage+0x10/0x10 __io_uring_show_fdinfo+0x9fe/0x1790 ? ksys_read+0xf7/0x1c0 ? do_syscall_64+0xa4/0x260 ? vsnprintf+0x591/0x1100 ? __pfx___io_uring_show_fdinfo+0x10/0x10 ? __pfx_vsnprintf+0x10/0x10 ? mutex_trylock+0xcf/0x130 ? __pfx_mutex_trylock+0x10/0x10 ? __pfx_show_fd_locks+0x10/0x10 ? io_uring_show_fdinfo+0x57/0x80 io_uring_show_fdinfo+0x57/0x80 seq_show+0x38c/0x690 seq_read_iter+0x3f7/0x1180 ? inode_set_ctime_current+0x160/0x4b0 seq_read+0x271/0x3e0 ? __pfx_seq_read+0x10/0x10 ? __pfx__raw_spin_lock+0x10/0x10 ? __mark_inode_dirty+0x402/0x810 ? selinux_file_permission+0x368/0x500 ? file_update_time+0x10f/0x160 vfs_read+0x177/0xa40 ? __pfx___handle_mm_fault+0x10/0x10 ? __pfx_vfs_read+0x10/0x10 ? mutex_lock+0x81/0xe0 ? __pfx_mutex_lock+0x10/0x10 ? fdget_pos+0x24d/0x4b0 ksys_read+0xf7/0x1c0 ? __pfx_ksys_read+0x10/0x10 ? do_user_addr_fault+0x43b/0x9c0 do_syscall_64+0xa4/0x260 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f0f74170fc9 Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 8 RSP: 002b:00007fffece049e8 EFLAGS: 00000206 ORIG_RAX: 0000000000000000 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f0f74170fc9 RDX: 0000000000001000 RSI: 00007fffece049f0 RDI: 0000000000000004 RBP: 00007fffece05ad0 R08: 0000000000000000 R09: 00007fffece04d90 R10: 0000000000000000 R11: 0000000000000206 R12: 00005651720a1100 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 </TASK> Allocated by task 298: kasan_save_stack+0x33/0x60 kasan_save_track+0x14/0x30 __kasan_slab_alloc+0x6e/0x70 kmem_cache_alloc_node_noprof+0xe8/0x330 copy_process+0x376/0x5e00 create_io_thread+0xab/0xf0 io_sq_offload_create+0x9ed/0xf20 io_uring_setup+0x12b0/0x1cc0 do_syscall_64+0xa4/0x260 entry_SYSCALL_64_after_hwframe+0x77/0x7f Freed by task 22: kasan_save_stack+0x33/0x60 kasan_save_track+0x14/0x30 kasan_save_free_info+0x3b/0x60 __kasan_slab_free+0x37/0x50 kmem_cache_free+0xc4/0x360 rcu_core+0x5ff/0x19f0 handle_softirqs+0x18c/0x530 run_ksoftirqd+0x20/0x30 smpboot_thread_fn+0x287/0x6c0 kthread+0x30d/0x630 ret_from_fork+0xef/0x1a0 ret_from_fork_asm+0x1a/0x30 Last potentially related work creation: kasan_save_stack+0x33/0x60 kasan_record_aux_stack+0x8c/0xa0 __call_rcu_common.constprop.0+0x68/0x940 __schedule+0xff2/0x2930 __cond_resched+0x4c/0x80 mutex_lock+0x5c/0xe0 io_uring_del_tctx_node+0xe1/0x2b0 io_uring_clean_tctx+0xb7/0x160 io_uring_cancel_generic+0x34e/0x760 do_exit+0x240/0x2350 do_group_exit+0xab/0x220 __x64_sys_exit_group+0x39/0x40 x64_sys_call+0x1243/0x1840 do_syscall_64+0xa4/0x260 entry_SYSCALL_64_after_hwframe+0x77/0x7f The buggy address belongs to the object at ffff88810de2cb00 which belongs to the cache task_struct of size 3712 The buggy address is located 1992 bytes inside of freed 3712-byte region [ffff88810de2cb00, ffff88810de2d980) which is caused by the task_struct pointed to by sq->thread being released while it is being used in the function __io_uring_show_fdinfo(). Holding ctx->uring_lock does not prevent ehre relase or exit of sq->thread. Fix this by assigning and looking up ->thread under RCU, and grabbing a reference to the task_struct. This e ---truncated---

Published
Jul 3, 2025
Updated
Aug 5, 2026
EPSS
0.1% · 9th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

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

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.

Follow CVE-2025-38106

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
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.

VendorProduct
linuxlinux kernel

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

    • 6.9affected
    • 3fcb9d17206e31630f802a3ab52081d1342b8ed9 and later · before af8c13f9ee040b9a287ba246cf0055f7c77b7cc8affected · git
    • 3fcb9d17206e31630f802a3ab52081d1342b8ed9 and later · before d0932758a0a77b38ba1b39564f3b7aba12407061affected · git
    • 3fcb9d17206e31630f802a3ab52081d1342b8ed9 and later · before ac0b8b327a5677dc6fecdf353d808161525b1ff0affected · git
    • before 6.9not affected · semver
    • 6.12.34 and later · up to and including 6.12.*not affected · semver
    • 6.15.3 and later · up to and including 6.15.*not affected · semver
    • 6.16 and laternot affected · original_commit_for_fix

Affected versions

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

  • linux linux kernel6.9 and later · before 6.12.34
  • linux linux kernel6.13 and later · before 6.15.3
  • linux linux kernel6.16

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-124.43.1.el10_16.12.0-124.43.1.el10_1
AlmaLinux:10kernel-docbefore 6.12.0-124.43.1.el10_16.12.0-124.43.1.el10_1
AlmaLinux:9kernelbefore 5.14.0-611.38.1.el9_75.14.0-611.38.1.el9_7
AlmaLinux:9kernel-64kbefore 5.14.0-611.38.1.el9_75.14.0-611.38.1.el9_7
AlmaLinux:9kernel-64k-corebefore 5.14.0-611.38.1.el9_75.14.0-611.38.1.el9_7
AlmaLinux:9kernel-64k-debugbefore 5.14.0-611.38.1.el9_75.14.0-611.38.1.el9_7
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-611.38.1.el9_75.14.0-611.38.1.el9_7
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-611.38.1.el9_75.14.0-611.38.1.el9_7
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-611.38.1.el9_75.14.0-611.38.1.el9_7
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-611.38.1.el9_75.14.0-611.38.1.el9_7
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-611.38.1.el9_75.14.0-611.38.1.el9_7
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-611.38.1.el9_75.14.0-611.38.1.el9_7
AlmaLinux:9kernel-64k-develbefore 5.14.0-611.38.1.el9_75.14.0-611.38.1.el9_7
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-611.38.1.el9_75.14.0-611.38.1.el9_7
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-611.38.1.el9_75.14.0-611.38.1.el9_7
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-611.38.1.el9_75.14.0-611.38.1.el9_7
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-611.38.1.el9_75.14.0-611.38.1.el9_7
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-611.38.1.el9_75.14.0-611.38.1.el9_7
AlmaLinux:9kernel-corebefore 5.14.0-611.38.1.el9_75.14.0-611.38.1.el9_7
AlmaLinux:9kernel-cross-headersbefore 5.14.0-611.38.1.el9_75.14.0-611.38.1.el9_7
AlmaLinux:9kernel-debugbefore 5.14.0-611.38.1.el9_75.14.0-611.38.1.el9_7
AlmaLinux:9kernel-debug-corebefore 5.14.0-611.38.1.el9_75.14.0-611.38.1.el9_7
AlmaLinux:9kernel-debug-develbefore 5.14.0-611.38.1.el9_75.14.0-611.38.1.el9_7
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-611.38.1.el9_75.14.0-611.38.1.el9_7

+96

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-38098Jul 3, 2025 · drm/amd/display: Don't treat wb connector as physical in create_validate_stream_for_sink
    22Monitor
  • ← EarlierCVE-2025-38101Jul 3, 2025 · ring-buffer: Fix buffer locking in ring_buffer_subbuf_order_set()
    31Monitor
  • Later →CVE-2025-38109Jul 3, 2025 · net/mlx5: Fix ECVF vports unload on shutdown flow
    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 / packageFixed versionSource
Linux Linuxac0b8b327a5677dc6fecdf353d808161525b1ff0Vendor (CNA)
Linux Linuxaf8c13f9ee040b9a287ba246cf0055f7c77b7cc8Vendor (CNA)
Linux Linuxd0932758a0a77b38ba1b39564f3b7aba12407061Vendor (CNA)
almalinux:kernel5.14.0-611.38.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-611.38.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-611.38.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-611.38.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-611.38.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-611.38.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-611.38.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-611.38.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-611.38.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-611.38.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-611.38.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-611.38.1.el9_7 · AlmaLinux:9Package registry (OSV)
debian:linux6.12.35-1 · Debian:13Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-570.92.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-570.92.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-570.92.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-570.92.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-570.92.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-570.92.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-570.92.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-570.92.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-570.92.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-570.92.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-570.92.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-ppc64le0:5.14.0-570.92.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage 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.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

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.

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

Vulnerable

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

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&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.

References

All records