CVE-2025-21823

一、漏洞信息
 漏洞编号：[CVE-2025-21823](https://nvd.nist.gov/vuln/detail/CVE-2025-21823)
 漏洞归属组件：[kernel](https://gitee.com/src-openeuler/kernel)
 漏洞归属的版本：4.19.140,4.19.194,4.19.90,5.10.0,6.1.19,6.1.8,6.4.0,6.6.0
 CVSS V3.0分值：
  BaseScore：N/A None
  Vector：CVSS：3.0/
 漏洞简述：
  In the Linux kernel, the following vulnerability has been resolved:batman-adv: Drop unmanaged ELP metric workerThe ELP worker needs to calculate new metric values for all neighbors reachable  over an interface. Some of the used metric sources requirelocks which might need to sleep. This sleep is incompatible with the RCUlist iterator used for the recorded neighbors. The initial approach to workaround of this problem was to queue another work item per neighbor and thenrun this in a new context.Even when this solved the RCU vs might_sleep() conflict, it has a majorproblems: Nothing was stopping the work item in case it is not neededanymore - for example because one of the related interfaces was removed orthe batman-adv module was unloaded - resulting in potential invalid memoryaccesses.Directly canceling the metric worker also has various problems:* cancel_work_sync for a to-be-deactivated interface is called with  rtnl_lock held. But the code in the ELP metric worker also tries to use  rtnl_lock() - which will never return in this case. This also means that  cancel_work_sync would never return because it is waiting for the worker  to finish.* iterating over the neighbor list for the to-be-deactivated interface is  currently done using the RCU specific methods. Which means that it is  possible to miss items when iterating over it without the associated  spinlock - a behaviour which is acceptable for a periodic metric check  but not for a cleanup routine (which must  stop  all still running  workers)The better approch is to get rid of the per interface neighbor metricworker and handle everything in the interface worker. The original problemsare solved by:* creating a list of neighbors which require new metric information inside  the RCU protected context, gathering the metric according to the new list  outside the RCU protected context* only use rcu_trylock inside metric gathering code to avoid a deadlock  when the cancel_delayed_work_sync is called in the interface removal code  (which is called with the rtnl_lock held)
 漏洞公开时间：2025-02-28 04:16:04
 漏洞创建时间：2025-02-28 10:21:05
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2025-21823
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/0fdc3c166ac17b26014313fa2b93696354511b24 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/1c334629176c2d644befc31a20d4bf75542f7631 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/3c0e0aecb78cb2a2ca1dc701982d08fedb088dc6 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/781a06fd265a8151f7601122d9c2e985663828ff |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/8c8ecc98f5c65947b0070a24bac11e12e47cc65d |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/a0019971f340ae02ba54cf1861f72da7e03e6b66 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/a7aa2317285806640c844acd4cd2cd768e395264 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/af264c2a9adc37f4bdf88ca7f3affa15d8c7de9e |  |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2025-21823 | https://bugzilla.suse.com/show_bug.cgi?id=1238475 |
| suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2025-21823 | https://bugzilla.suse.com/show_bug.cgi?id=1238475 |
| suse_bugzilla | https://git.kernel.org/stable/c/0fdc3c166ac17b26014313fa2b93696354511b24 | https://bugzilla.suse.com/show_bug.cgi?id=1238475 |
| suse_bugzilla | https://git.kernel.org/stable/c/781a06fd265a8151f7601122d9c2e985663828ff | https://bugzilla.suse.com/show_bug.cgi?id=1238475 |
| suse_bugzilla | https://git.kernel.org/stable/c/8c8ecc98f5c65947b0070a24bac11e12e47cc65d | https://bugzilla.suse.com/show_bug.cgi?id=1238475 |
| suse_bugzilla | https://git.kernel.org/stable/c/a7aa2317285806640c844acd4cd2cd768e395264 | https://bugzilla.suse.com/show_bug.cgi?id=1238475 |
| suse_bugzilla | https://git.kernel.org/stable/c/af264c2a9adc37f4bdf88ca7f3affa15d8c7de9e | https://bugzilla.suse.com/show_bug.cgi?id=1238475 |
| suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2025/CVE-2025-21823.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1238475 |
| suse_bugzilla | https://bugzilla.redhat.com/show_bug.cgi?id=2348900 | https://bugzilla.suse.com/show_bug.cgi?id=1238475 |
| redhat_bugzilla | https://lore.kernel.org/linux-cve-announce/2025022708-CVE-2025-21823-9027@gregkh/T | https://bugzilla.redhat.com/show_bug.cgi?id=2348900 |

</details>

漏洞分析指导链接：
  https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
 漏洞数据来源:
  openBrain开源漏洞感知系统
 漏洞补丁信息：
  <details>
<summary>详情(点击展开)</summary>

| 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源  |
| ------- | -------- | ------- | -------- | --------- |
| linux_kernel | 6.1.129 | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=781a06fd265a8151f7601122d9c2e985663828ffIssue | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c833484e5f3872a38fe232c663586069d5ad9645 | linuxkernelcves |
| linux_kernel | 6.6.79 | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a7aa2317285806640c844acd4cd2cd768e395264Issue | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c833484e5f3872a38fe232c663586069d5ad9645 | linuxkernelcves |
| linux_kernel | 6.12.16 | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=0fdc3c166ac17b26014313fa2b93696354511b24Issue | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c833484e5f3872a38fe232c663586069d5ad9645 | linuxkernelcves |
| linux_kernel | 6.13.4 | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=af264c2a9adc37f4bdf88ca7f3affa15d8c7de9eIssue | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c833484e5f3872a38fe232c663586069d5ad9645 | linuxkernelcves |
| linux_kernel | 6.14-rc3 | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=8c8ecc98f5c65947b0070a24bac11e12e47cc65dPlease | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c833484e5f3872a38fe232c663586069d5ad9645 | linuxkernelcves |

</details>

二、漏洞分析结构反馈
 影响性分析说明：
  In the Linux kernel, the following vulnerability has been resolved:batman-adv: Drop unmanaged ELP metric workerThe ELP worker needs to calculate new metric values for all neighbors reachable  over an interface. Some of the used metric sources requirelocks which might need to sleep. This sleep is incompatible with the RCUlist iterator used for the recorded neighbors. The initial approach to workaround of this problem was to queue another work item per neighbor and thenrun this in a new context.Even when this solved the RCU vs might_sleep() conflict, it has a majorproblems: Nothing was stopping the work item in case it is not neededanymore - for example because one of the related interfaces was removed orthe batman-adv module was unloaded - resulting in potential invalid memoryaccesses.Directly canceling the metric worker also has various problems:* cancel_work_sync for a to-be-deactivated interface is called with  rtnl_lock held. But the code in the ELP metric worker also tries to use  rtnl_lock() - which will never return in this case. This also means that  cancel_work_sync would never return because it is waiting for the worker  to finish.* iterating over the neighbor list for the to-be-deactivated interface is  currently done using the RCU specific methods. Which means that it is  possible to miss items when iterating over it without the associated  spinlock - a behaviour which is acceptable for a periodic metric check  but not for a cleanup routine (which must  stop  all still running  workers)The better approch is to get rid of the per interface neighbor metricworker and handle everything in the interface worker. The original problemsare solved by:* creating a list of neighbors which require new metric information inside  the RCU protected context, gathering the metric according to the new list  outside the RCU protected context* only use rcu_trylock inside metric gathering code to avoid a deadlock  when the cancel_delayed_work_sync is called in the interface removal code  (which is called with the rtnl_lock held)
 openEuler评分：
  3.9
 Vector：CVSS：3.0/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L
 受影响版本排查(受影响/不受影响)：
  1.openEuler-20.03-LTS-SP4(4.19.90):受影响
2.openEuler-22.03-LTS-SP3:受影响
3.openEuler-22.03-LTS-SP4:受影响
4.openEuler-24.03-LTS:受影响
5.openEuler-24.03-LTS-SP1:受影响
6.master:不受影响
7.openEuler-24.03-LTS-Next:不受影响

修复是否涉及abi变化(是/否)：
  1.master:否
2.openEuler-20.03-LTS-SP4(4.19.90):否
3.openEuler-22.03-LTS-SP3:否
4.openEuler-22.03-LTS-SP4:否
5.openEuler-24.03-LTS:否
6.openEuler-24.03-LTS-Next:否
7.openEuler-24.03-LTS-SP1:否

原因说明：
  1.openEuler-22.03-LTS-SP3:正常修复
2.openEuler-22.03-LTS-SP4:正常修复
3.openEuler-24.03-LTS:正常修复
4.openEuler-24.03-LTS-SP1:正常修复
5.openEuler-20.03-LTS-SP4(4.19.90):不修复-超出修复范围
6.master:不受影响-漏洞代码不能被攻击者触发
7.openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发

三、漏洞修复
安全公告链接：https://www.openeuler.org/zh/security/safety-bulletin/detail/?id=openEuler-SA-2025-1410

src-openEuler/kernel

内容风险标识

评论 (11)

src-openEuler/kernel .gitee-modal { width: 500px !important; }

内容风险标识

CVE-2025-21823

评论 (11)

搜索帮助

src-openEuler/kernel