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

Goal: 1000 CNY · Raised: 1336 CNY

100%

CVE-2025-38525— rxrpc: Fix irq-disabled in local_bh_enable()

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所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于rxrpc在IRQ禁用时调用local_bh_enable,可能导致警告。

CVSS 7.5 · High EPSS 0.36% · P29

Possible ATT&CK Techniques 1 AI

T1068 · Exploitation for Privilege Escalation

Affected Version Matrix 12

VendorProduct Version RangeStatus
Linux Linux 77433b730970ca6e51d03016e830d8ab1b22685a< d94b82d452ca27a200cd67660dc48476386651d8 affected
09c59a82298f424f6212c67fbea531853e88ce6c< 8ac0b3baa7d8f732bd9e5cbf1d8b57e4802c6b36 affected
a2ea9a9072607c2fd6442bd1ffb4dbdbf882aed7< 2029f21f10dedb88c0f86abffcf8d6c21dcf6040 affected
a2ea9a9072607c2fd6442bd1ffb4dbdbf882aed7< e4d2878369d590bf8455e3678a644e503172eafa affected
6.6.148< 6.6.151 affected
6.12.101< 6.12.103 affected
6.14 affected
< 6.14 unaffected
… +4 more rows
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2025-38525

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
rxrpc: Fix irq-disabled in local_bh_enable()
Source: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix irq-disabled in local_bh_enable() The rxrpc_assess_MTU_size() function calls down into the IP layer to find out the MTU size for a route. When accepting an incoming call, this is called from rxrpc_new_incoming_call() which holds interrupts disabled across the code that calls down to it. Unfortunately, the IP layer uses local_bh_enable() which, config dependent, throws a warning if IRQs are enabled: WARNING: CPU: 1 PID: 5544 at kernel/softirq.c:387 __local_bh_enable_ip+0x43/0xd0 ... RIP: 0010:__local_bh_enable_ip+0x43/0xd0 ... Call Trace: <TASK> rt_cache_route+0x7e/0xa0 rt_set_nexthop.isra.0+0x3b3/0x3f0 __mkroute_output+0x43a/0x460 ip_route_output_key_hash+0xf7/0x140 ip_route_output_flow+0x1b/0x90 rxrpc_assess_MTU_size.isra.0+0x2a0/0x590 rxrpc_new_incoming_peer+0x46/0x120 rxrpc_alloc_incoming_call+0x1b1/0x400 rxrpc_new_incoming_call+0x1da/0x5e0 rxrpc_input_packet+0x827/0x900 rxrpc_io_thread+0x403/0xb60 kthread+0x2f7/0x310 ret_from_fork+0x2a/0x230 ret_from_fork_asm+0x1a/0x30 ... hardirqs last enabled at (23): _raw_spin_unlock_irq+0x24/0x50 hardirqs last disabled at (24): _raw_read_lock_irq+0x17/0x70 softirqs last enabled at (0): copy_process+0xc61/0x2730 softirqs last disabled at (25): rt_add_uncached_list+0x3c/0x90 Fix this by moving the call to rxrpc_assess_MTU_size() out of rxrpc_init_peer() and further up the stack where it can be done without interrupts disabled. It shouldn't be a problem for rxrpc_new_incoming_call() to do it after the locks are dropped as pmtud is going to be performed by the I/O thread - and we're in the I/O thread at this point.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于rxrpc在IRQ禁用时调用local_bh_enable,可能导致警告。
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 77433b730970ca6e51d03016e830d8ab1b22685a ~ d94b82d452ca27a200cd67660dc48476386651d8 -
Linux Linux 6.14 -

II. Public POCs for CVE-2025-38525

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

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2025-38525

登录查看更多情报信息。

Patches & Fixes for CVE-2025-38525 (3)

Same Patch Batch · Linux · 2025-08-16 · 59 CVEs total

CVE-2025-38533 9.8 CRITICAL net: libwx: fix the using of Rx buffer DMA
CVE-2025-38527 9.8 CRITICAL smb: client: fix use-after-free in cifs_oplock_break
CVE-2025-38552 9.4 CRITICAL mptcp: plug races between subflow fail and subflow creation
CVE-2023-3867 9.1 CRITICAL ksmbd: fix out of bounds read in smb2_sess_setup
CVE-2023-4515 9.1 CRITICAL ksmbd: validate command request size
CVE-2023-32249 9.1 CRITICAL ksmbd: not allow guest user on multichannel
CVE-2025-38512 8.8 HIGH wifi: prevent A-MSDU attacks in mesh networks
CVE-2025-38511 8.8 HIGH drm/xe/pf: Clear all LMTT pages on alloc
CVE-2023-4130 8.1 HIGH ksmbd: fix wrong next length validation of ea buffer in smb2_set_ea()
CVE-2023-3865 8.1 HIGH ksmbd: fix out-of-bound read in smb2_write
CVE-2025-38550 7.8 HIGH ipv6: mcast: Delay put pmc->idev in mld_del_delrec()
CVE-2025-38502 7.8 HIGH bpf: Fix oob access in cgroup local storage
CVE-2025-38532 7.8 HIGH net: libwx: properly reset Rx ring descriptor
CVE-2025-38542 7.8 HIGH net: appletalk: Fix device refcount leak in atrtr_create()
CVE-2025-38536 7.8 HIGH net: airoha: fix potential use-after-free in airoha_npu_get()
CVE-2025-38539 7.8 HIGH tracing: Add down_write(trace_event_sem) when adding trace event
CVE-2025-38501 7.5 HIGH ksmbd: limit repeated connections from clients with the same IP
CVE-2025-38514 7.5 HIGH rxrpc: Fix oops due to non-existence of prealloc backlog struct
CVE-2025-38526 7.5 HIGH ice: add NULL check in eswitch lag check
CVE-2025-38523 7.5 HIGH cifs: Fix the smbd_response slab to allow usercopy

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

IV. Related Vulnerabilities

V. Comments for CVE-2025-38525

No comments yet


Leave a comment