Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

CVE-2026-89747— tracing: Fix use-after-free in trace_pipe read on sub-buffer order change

Quick assessment

Affected
Linux Linux
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Linux kernel是美国Linux基金会开源的一个操作系统内核。 Linux kernel存在安全漏洞,该漏洞源于在trace_pipe读取过程中,写入buffer_subbuf_size_kb触发ring_buffer_subbuf_order_set()释放包括reader page在内的子缓冲区后,读者仍解引用已释放的事件指针,可能导致释放后重用,造成内存损坏或系统崩溃。

CVSS 7.8 · High EPSS 0.16% · P5

Affected Version Matrix 10

VendorProduct Version RangeStatus
Linux Linux f9b94daa542a8d2532f0930f01cd9aec2d19621b< 05ebe1e1d7d38c2612bacfefe043a33572ae34cb affected
f9b94daa542a8d2532f0930f01cd9aec2d19621b< ddbe921ed16a0ad2d9e09574c3f3aabec7528325 affected
f9b94daa542a8d2532f0930f01cd9aec2d19621b< 7a49d19ff9baaf61217e5ec14199c18bc2d93ee4 affected
f9b94daa542a8d2532f0930f01cd9aec2d19621b< 372f8534244d632ad5118e8a87a11291b01712d3 affected
6.8 affected
< 6.8 unaffected
6.12.109≤ 6.12.* unaffected
6.18.50≤ 6.18.* unaffected
… +2 more rows
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-89747

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
tracing: Fix use-after-free in trace_pipe read on sub-buffer order change
Source: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: tracing: Fix use-after-free in trace_pipe read on sub-buffer order change Writing to buffer_subbuf_size_kb calls ring_buffer_subbuf_order_set(), which frees every sub-buffer of the ring buffer, including the reader page, and replaces them with newly allocated ones. Readers of trace_pipe hold pointers into those pages. ring_buffer_peek() looks up an event under cpu_buffer->reader_lock but returns the event pointer after dropping the lock, and peek_next_entry() then calls ring_buffer_event_length() and ring_buffer_event_data() on it. If the sub-buffer order is changed in that window, the reader dereferences freed memory: BUG: KASAN: use-after-free in ring_buffer_peek+0x3e0/0x430 Read of size 1 at addr ffff88802a4cf010 by task syz-executor989/6002 Freed by: free_buffer_page kernel/trace/ring_buffer.c:398 [inline] ring_buffer_subbuf_order_set+0x1325/0x18e0 kernel/trace/ring_buffer.c:7444 buffer_subbuf_size_write+0x182/0x280 kernel/trace/trace.c:8221 Take trace_access_lock(RING_BUFFER_ALL_CPUS) around the order change. This is the lock trace_pipe readers already hold across their entire peek-and-print loop, so the swap can no longer race with a reader that is dereferencing a peeked event.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Source: CVE Program / CVE List V5
Vulnerability Type
N/A
Source: CVE Program / CVE List V5
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会开源的一个操作系统内核。 Linux kernel存在安全漏洞,该漏洞源于在trace_pipe读取过程中,写入buffer_subbuf_size_kb触发ring_buffer_subbuf_order_set()释放包括reader page在内的子缓冲区后,读者仍解引用已释放的事件指针,可能导致释放后重用,造成内存损坏或系统崩溃。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
Linux Linux f9b94daa542a8d2532f0930f01cd9aec2d19621b ~ 05ebe1e1d7d38c2612bacfefe043a33572ae34cb -
Linux Linux 6.8 -

II. Public POCs for CVE-2026-89747

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-89747

请登录查看更多情报信息。

Patches & Fixes for CVE-2026-89747 (4)

Same Patch Batch · Linux · 2026-09-11 · 431 CVEs total

CVE-2026-89669 9.8 CRITICAL nfsd: initialize copy-notify stateid before publishing it
CVE-2026-89536 9.8 CRITICAL SUNRPC: wait for in-flight client TLS handshake callback
CVE-2026-89533 9.8 CRITICAL svcrdma: Fix offset arithmetic in read_chunk_range
CVE-2026-81002 9.8 CRITICAL xdp: fix zero-copy frame layout
CVE-2026-89643 9.8 CRITICAL audit: avoid dropping live tree ref on fsnotify rule autoremove
CVE-2026-89526 9.8 CRITICAL svcrdma: Validate Read chunk positions before reconstruction
CVE-2026-89652 9.8 CRITICAL ceph: bound copied dentry name length in NFS export get_name
CVE-2026-89651 9.8 CRITICAL ceph: bound MDSCapAuth path and fs_name decode in handle_session()
CVE-2026-89653 9.8 CRITICAL ceph: reject export_targets ranks >= CEPH_MAX_MDS in mdsmap decode
CVE-2026-89654 9.8 CRITICAL ceph: fix UAF in check_new_map() on session freed during unlock
CVE-2026-89656 9.8 CRITICAL libceph: reject buckets with mismatched CRUSH ids
CVE-2026-89655 9.8 CRITICAL ceph: fix UAF in __kick_flushing_caps() on cf entry freed during unlock
CVE-2026-89712 9.8 CRITICAL NFSD: restart ssc_expire_umount walk after dropping nfsd_ssc_lock
CVE-2026-89658 9.8 CRITICAL NFSD: Prevent client use-after-free during NFSv4.0 revoked-state cleanup
CVE-2026-89660 9.8 CRITICAL NFSD: Prevent client use-after-free during admin state revocation
CVE-2026-89659 9.8 CRITICAL NFSD: Prevent client use-after-free during delegation revoke
CVE-2026-89708 9.8 CRITICAL nfsd: RCU-protect cl_cb_session to fix use-after-free on session teardown
CVE-2026-89662 9.8 CRITICAL NFSD: Prevent lock owner use-after-free during client teardown
CVE-2026-89689 9.8 CRITICAL nfsd: don't free session slots that are still in use
CVE-2026-89686 9.8 CRITICAL nfsd: fix BUG_ON in nfsd4_alloc_layout_stateid on racing delegation revoke

Showing top 20 of 431 CVEs. View all on vendor page &rarr; →

IV. Related Vulnerabilities

V. Comments for CVE-2026-89747

No comments yet


Leave a comment