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

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2024-57888— workqueue: Do not warn when cancelling WQ_MEM_RECLAIM work from !WQ_MEM_RECLAIM worker

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存在安全漏洞。目前尚无此漏洞的相关信息，请随时关注CNNVD或厂商公告。

AI Predicted 5.3 Difficulty: Theoretical EPSS 0.21% · P10

Possible ATT&CK Techniques 1 AI

T1053 · Scheduled Task/Job

Affected Version Matrix 8

VendorProduct Version RangeStatus
Linux Linux fca839c00a12d682cb59b3b620d109a1d850b262< 1fd2a57dcb4de3cb40844a29c71b5d7b46a84334 affected
fca839c00a12d682cb59b3b620d109a1d850b262< ffb231471a407c96e114070bf828cd2378fdf431 affected
fca839c00a12d682cb59b3b620d109a1d850b262< de35994ecd2dd6148ab5a6c5050a1670a04dec77 affected
4.5 affected
< 4.5 unaffected
6.6.72≤ 6.6.* unaffected
6.12.9≤ 6.12.* unaffected
6.13≤ * unaffected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2024-57888

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
workqueue: Do not warn when cancelling WQ_MEM_RECLAIM work from !WQ_MEM_RECLAIM worker
Source: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: workqueue: Do not warn when cancelling WQ_MEM_RECLAIM work from !WQ_MEM_RECLAIM worker After commit 746ae46c1113 ("drm/sched: Mark scheduler work queues with WQ_MEM_RECLAIM") amdgpu started seeing the following warning: [ ] workqueue: WQ_MEM_RECLAIM sdma0:drm_sched_run_job_work [gpu_sched] is flushing !WQ_MEM_RECLAIM events:amdgpu_device_delay_enable_gfx_off [amdgpu] ... [ ] Workqueue: sdma0 drm_sched_run_job_work [gpu_sched] ... [ ] Call Trace: [ ] <TASK> ... [ ] ? check_flush_dependency+0xf5/0x110 ... [ ] cancel_delayed_work_sync+0x6e/0x80 [ ] amdgpu_gfx_off_ctrl+0xab/0x140 [amdgpu] [ ] amdgpu_ring_alloc+0x40/0x50 [amdgpu] [ ] amdgpu_ib_schedule+0xf4/0x810 [amdgpu] [ ] ? drm_sched_run_job_work+0x22c/0x430 [gpu_sched] [ ] amdgpu_job_run+0xaa/0x1f0 [amdgpu] [ ] drm_sched_run_job_work+0x257/0x430 [gpu_sched] [ ] process_one_work+0x217/0x720 ... [ ] </TASK> The intent of the verifcation done in check_flush_depedency is to ensure forward progress during memory reclaim, by flagging cases when either a memory reclaim process, or a memory reclaim work item is flushed from a context not marked as memory reclaim safe. This is correct when flushing, but when called from the cancel(_delayed)_work_sync() paths it is a false positive because work is either already running, or will not be running at all. Therefore cancelling it is safe and we can relax the warning criteria by letting the helper know of the calling context. References: 746ae46c1113 ("drm/sched: Mark scheduler work queues with WQ_MEM_RECLAIM")
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存在安全漏洞。目前尚无此漏洞的相关信息，请随时关注CNNVD或厂商公告。
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 fca839c00a12d682cb59b3b620d109a1d850b262 ~ 1fd2a57dcb4de3cb40844a29c71b5d7b46a84334 -
Linux Linux 4.5 -

II. Public POCs for CVE-2024-57888

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

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2024-57888

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

Patches & Fixes for CVE-2024-57888 (3)

Same Patch Batch · Linux · 2025-01-15 · 32 CVEs total

CVE-2024-57882 9.8 CRITICAL mptcp: fix TCP options overflow.
CVE-2024-36476 9.8 CRITICAL RDMA/rtrs: Ensure 'ib_sge list' is accessible
CVE-2024-57802 9.4 CRITICAL netrom: check buffer length before accessing it
CVE-2025-21629 8.2 HIGH net: reenable NETIF_F_IPV6_CSUM offload for BIG TCP packets
CVE-2024-57883 7.8 HIGH mm: hugetlb: independent PMD page table shared count
CVE-2024-57857 7.8 HIGH RDMA/siw: Remove direct link to net_device
CVE-2024-57801 7.8 HIGH net/mlx5e: Skip restore TC rules for vport rep without loaded flag
CVE-2024-57795 7.8 HIGH RDMA/rxe: Remove the direct link to net_device
CVE-2024-39282 7.8 HIGH net: wwan: t7xx: Fix FSM command timeout issue
CVE-2024-57896 7.8 HIGH btrfs: flush delalloc workers queue before stopping cleaner kthread during unmount
CVE-2024-57893 7.8 HIGH ALSA: seq: oss: Fix races at processing SysEx messages
CVE-2024-57887 7.8 HIGH drm: adv7511: Fix use-after-free in adv7533_attach_dsi()
CVE-2024-57899 7.6 HIGH wifi: mac80211: fix mbss changed flags corruption on 32 bit systems
CVE-2024-57902 7.3 HIGH af_packet: fix vlan_get_tci() vs MSG_PEEK
CVE-2024-57901 7.3 HIGH af_packet: fix vlan_get_protocol_dgram() vs MSG_PEEK
CVE-2024-57895 7.1 HIGH ksmbd: set ATTR_CTIME flags when setting mtime
CVE-2024-57884 mm: vmscan: account for free pages to prevent infinite Loop in throttle_direct_reclaim()
CVE-2024-57844 drm/xe: Fix fault on fd close after unbind
CVE-2024-57841 net: fix memory leak in tcp_conn_request()
CVE-2024-57885 mm/kmemleak: fix sleeping function called from invalid context at print message

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

IV. Related Vulnerabilities

Same product: Linux
Same vendor: Linux

V. Comments for CVE-2024-57888

No comments yet

Leave a comment