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

Goal: 1000 CNY · Raised: 1359 CNY

100%

CVE-2025-21983— mm/slab/kvfree_rcu: Switch to WQ_MEM_RECLAIM wq

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存在安全漏洞,该漏洞源于mm slab kvfree_rcu模块未使用WQ_MEM_RECLAIM工作队列。

AI Predicted 3.3 Difficulty: Trivial EPSS 0.20% · P9

Possible ATT&CK Techniques 1 AI

T1496 · Resource Hijacking

Affected Version Matrix 8

VendorProduct Version RangeStatus
Linux Linux 6c6c47b063b593785202be158e61fe5c827d6677< a74979dce9e9c61f6d797c3761020252c4d8dc63 affected
6c6c47b063b593785202be158e61fe5c827d6677< 656e35bf66a11e1adde44c4c12050086dc39f241 affected
6c6c47b063b593785202be158e61fe5c827d6677< dfd3df31c9db752234d7d2e09bef2aeabb643ce4 affected
6.12 affected
< 6.12 unaffected
6.12.20≤ 6.12.* unaffected
6.13.8≤ 6.13.* unaffected
6.14≤ * unaffected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2025-21983

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
mm/slab/kvfree_rcu: Switch to WQ_MEM_RECLAIM wq
Source: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: mm/slab/kvfree_rcu: Switch to WQ_MEM_RECLAIM wq Currently kvfree_rcu() APIs use a system workqueue which is "system_unbound_wq" to driver RCU machinery to reclaim a memory. Recently, it has been noted that the following kernel warning can be observed: <snip> workqueue: WQ_MEM_RECLAIM nvme-wq:nvme_scan_work is flushing !WQ_MEM_RECLAIM events_unbound:kfree_rcu_work WARNING: CPU: 21 PID: 330 at kernel/workqueue.c:3719 check_flush_dependency+0x112/0x120 Modules linked in: intel_uncore_frequency(E) intel_uncore_frequency_common(E) skx_edac(E) ... CPU: 21 UID: 0 PID: 330 Comm: kworker/u144:6 Tainted: G E 6.13.2-0_g925d379822da #1 Hardware name: Wiwynn Twin Lakes MP/Twin Lakes Passive MP, BIOS YMM20 02/01/2023 Workqueue: nvme-wq nvme_scan_work RIP: 0010:check_flush_dependency+0x112/0x120 Code: 05 9a 40 14 02 01 48 81 c6 c0 00 00 00 48 8b 50 18 48 81 c7 c0 00 00 00 48 89 f9 48 ... RSP: 0018:ffffc90000df7bd8 EFLAGS: 00010082 RAX: 000000000000006a RBX: ffffffff81622390 RCX: 0000000000000027 RDX: 00000000fffeffff RSI: 000000000057ffa8 RDI: ffff88907f960c88 RBP: 0000000000000000 R08: ffffffff83068e50 R09: 000000000002fffd R10: 0000000000000004 R11: 0000000000000000 R12: ffff8881001a4400 R13: 0000000000000000 R14: ffff88907f420fb8 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff88907f940000(0000) knlGS:0000000000000000 CR2: 00007f60c3001000 CR3: 000000107d010005 CR4: 00000000007726f0 PKRU: 55555554 Call Trace: <TASK> ? __warn+0xa4/0x140 ? check_flush_dependency+0x112/0x120 ? report_bug+0xe1/0x140 ? check_flush_dependency+0x112/0x120 ? handle_bug+0x5e/0x90 ? exc_invalid_op+0x16/0x40 ? asm_exc_invalid_op+0x16/0x20 ? timer_recalc_next_expiry+0x190/0x190 ? check_flush_dependency+0x112/0x120 ? check_flush_dependency+0x112/0x120 __flush_work.llvm.1643880146586177030+0x174/0x2c0 flush_rcu_work+0x28/0x30 kvfree_rcu_barrier+0x12f/0x160 kmem_cache_destroy+0x18/0x120 bioset_exit+0x10c/0x150 disk_release.llvm.6740012984264378178+0x61/0xd0 device_release+0x4f/0x90 kobject_put+0x95/0x180 nvme_put_ns+0x23/0xc0 nvme_remove_invalid_namespaces+0xb3/0xd0 nvme_scan_work+0x342/0x490 process_scheduled_works+0x1a2/0x370 worker_thread+0x2ff/0x390 ? pwq_release_workfn+0x1e0/0x1e0 kthread+0xb1/0xe0 ? __kthread_parkme+0x70/0x70 ret_from_fork+0x30/0x40 ? __kthread_parkme+0x70/0x70 ret_from_fork_asm+0x11/0x20 </TASK> ---[ end trace 0000000000000000 ]--- <snip> To address this switch to use of independent WQ_MEM_RECLAIM workqueue, so the rules are not violated from workqueue framework point of view. Apart of that, since kvfree_rcu() does reclaim memory it is worth to go with WQ_MEM_RECLAIM type of wq because it is designed for this purpose.
Source: CVE Program / CVE List V5
CVSS Information
N/A
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存在安全漏洞,该漏洞源于mm slab kvfree_rcu模块未使用WQ_MEM_RECLAIM工作队列。
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 6c6c47b063b593785202be158e61fe5c827d6677 ~ a74979dce9e9c61f6d797c3761020252c4d8dc63 -
Linux Linux 6.12 -

II. Public POCs for CVE-2025-21983

# 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-21983

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

Same Patch Batch · Linux · 2025-04-01 · 93 CVEs total

CVE-2025-21954 9.8 CRITICAL netmem: prevent TX of unreadable skbs
CVE-2025-21927 9.8 CRITICAL nvme-tcp: fix potential memory corruption in nvme_tcp_recv_pdu()
CVE-2025-21955 8.8 HIGH ksmbd: prevent connection release during oplock break notification
CVE-2025-21946 8.8 HIGH ksmbd: fix out-of-bounds in parse_sec_desc()
CVE-2025-21945 8.8 HIGH ksmbd: fix use-after-free in smb2_lock
CVE-2025-21969 8.8 HIGH Bluetooth: L2CAP: Fix slab-use-after-free Read in l2cap_send_cmd
CVE-2025-21967 8.8 HIGH ksmbd: fix use-after-free in ksmbd_free_work_struct
CVE-2025-21972 8.8 HIGH net: mctp: unshare packets when reassembling
CVE-2025-21947 8.1 HIGH ksmbd: fix type confusion via race condition when using ipc_msg_send_request
CVE-2025-21896 7.8 HIGH fuse: revert back to __readahead_folio() for readahead
CVE-2025-21949 7.8 HIGH LoongArch: Set hugetlb mmap base address aligned with pmd size
CVE-2025-21979 7.8 HIGH wifi: cfg80211: cancel wiphy_work before freeing wiphy
CVE-2025-21899 7.8 HIGH tracing: Fix bad hist from corrupting named_triggers list
CVE-2025-21966 7.8 HIGH dm-flakey: Fix memory corruption in optional corrupt_bio_byte feature
CVE-2025-21926 7.8 HIGH net: gso: fix ownership in __udp_gso_segment
CVE-2025-21965 7.8 HIGH sched_ext: Validate prev_cpu in scx_bpf_select_cpu_dfl()
CVE-2025-21924 7.8 HIGH net: hns3: make sure ptp clock is unregister and freed if hclge_ptp_get_cycle returns an e
CVE-2025-21934 7.8 HIGH rapidio: fix an API misues when rio_add_net() fails
CVE-2025-21939 7.8 HIGH drm/xe/hmm: Don't dereference struct page pointers without notifier lock
CVE-2025-21958 7.8 HIGH Revert "openvswitch: switch to per-action label counting in conntrack"

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

IV. Related Vulnerabilities

V. Comments for CVE-2025-21983

No comments yet


Leave a comment