CVE-2025-39737 (CNNVD-202509-1646)

UNKNOWN
中文标题:
Linux kernel 安全漏洞
英文标题:
mm/kmemleak: avoid soft lockup in __kmemleak_do_cleanup()
CVSS分数: N/A
发布时间: 2025-09-11 16:52:12
漏洞类型: 其他
状态: PUBLISHED
数据质量分数: 0.40
数据版本: v5
漏洞描述
中文描述:

Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于__kmemleak_do_cleanup函数处理大量kmemleak对象时可能导致软锁定。

英文描述:

In the Linux kernel, the following vulnerability has been resolved: mm/kmemleak: avoid soft lockup in __kmemleak_do_cleanup() A soft lockup warning was observed on a relative small system x86-64 system with 16 GB of memory when running a debug kernel with kmemleak enabled. watchdog: BUG: soft lockup - CPU#8 stuck for 33s! [kworker/8:1:134] The test system was running a workload with hot unplug happening in parallel. Then kemleak decided to disable itself due to its inability to allocate more kmemleak objects. The debug kernel has its CONFIG_DEBUG_KMEMLEAK_MEM_POOL_SIZE set to 40,000. The soft lockup happened in kmemleak_do_cleanup() when the existing kmemleak objects were being removed and deleted one-by-one in a loop via a workqueue. In this particular case, there are at least 40,000 objects that need to be processed and given the slowness of a debug kernel and the fact that a raw_spinlock has to be acquired and released in __delete_object(), it could take a while to properly handle all these objects. As kmemleak has been disabled in this case, the object removal and deletion process can be further optimized as locking isn't really needed. However, it is probably not worth the effort to optimize for such an edge case that should rarely happen. So the simple solution is to call cond_resched() at periodic interval in the iteration loop to avoid soft lockup.

CWE类型:
CWE-401
标签:
(暂无数据)
受影响产品
厂商 产品 版本 版本范围 平台 CPE
Linux Linux - < 9f1f4e95031f84867c5821540466d62f88dab8ca - cpe:2.3:a:linux:linux:*:*:*:*:*:*:*:*
Linux Linux 5.4 - - cpe:2.3:a:linux:linux:5.4:*:*:*:*:*:*:*
linux linux_kernel * - - cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel 5.4 - - cpe:2.3:o:linux:linux_kernel:5.4:-:*:*:*:*:*:*
linux linux_kernel 6.17 - - cpe:2.3:o:linux:linux_kernel:6.17:rc1:*:*:*:*:*:*
debian debian_linux 11.0 - - cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*
解决方案
中文解决方案:
(暂无数据)
英文解决方案:
(暂无数据)
临时解决方案:
(暂无数据)
参考链接
无标题 OTHER
cve.org
访问
无标题 OTHER
cve.org
访问
无标题 OTHER
cve.org
访问
无标题 OTHER
cve.org
访问
无标题 OTHER
cve.org
访问
无标题 OTHER
cve.org
访问
无标题 OTHER
cve.org
访问
无标题 OTHER
cve.org
访问
无标题 OTHER
cve.org
访问
af854a3a-2127-422b-91ae-364da2661108 OTHER
nvd.nist.gov
访问
af854a3a-2127-422b-91ae-364da2661108 OTHER
nvd.nist.gov
访问
CVSS评分详情
暂无CVSS评分信息
时间信息
发布时间:
2025-09-11 16:52:12
修改时间:
2025-11-03 17:42:54
创建时间:
2025-11-11 15:40:29
更新时间:
2026-01-28 06:00:18
利用信息
暂无可利用代码信息
数据源详情
数据源 记录ID 版本 提取时间
CVE cve_CVE-2025-39737 2025-11-11 15:23:19 2025-11-11 07:40:29
NVD nvd_CVE-2025-39737 2025-11-11 15:01:02 2025-11-11 07:48:18
CNNVD cnnvd_CNNVD-202509-1646 2025-11-11 15:12:56 2025-11-11 08:00:10
版本与语言
当前版本: v5
主要语言: EN
支持语言:
ZH EN
安全公告
暂无安全公告信息
变更历史
v5 NVD
2026-01-28 06:00:18
affected_products_count: 2 → 6
查看详细变更
  • affected_products_count: 2 -> 6
v4 CVE
2026-01-12 02:11:41
affected_products_count: 1 → 2
查看详细变更
  • affected_products_count: 1 -> 2
v3 CNNVD
2025-11-11 16:00:10
vulnerability_type: 未提取 → 其他; severity: SeverityLevel.MEDIUM → SeverityLevel.UNKNOWN; cvss_score: 未提取 → 0.0; cnnvd_id: 未提取 → CNNVD-202509-1646; data_sources: ['cve', 'nvd'] → ['cnnvd', 'cve', 'nvd']
查看详细变更
  • vulnerability_type: 未提取 -> 其他
  • severity: SeverityLevel.MEDIUM -> SeverityLevel.UNKNOWN
  • cvss_score: 未提取 -> 0.0
  • cnnvd_id: 未提取 -> CNNVD-202509-1646
  • data_sources: ['cve', 'nvd'] -> ['cnnvd', 'cve', 'nvd']
v2 NVD
2025-11-11 15:48:18
affected_products_count: 10 → 1; references_count: 9 → 11; data_sources: ['cve'] → ['cve', 'nvd']
查看详细变更
  • affected_products_count: 10 -> 1
  • references_count: 9 -> 11
  • data_sources: ['cve'] -> ['cve', 'nvd']