CVE-2024-43876

一、漏洞信息
 漏洞编号：[CVE-2024-43876](https://nvd.nist.gov/vuln/detail/CVE-2024-43876)
 漏洞归属组件：[kernel](https://gitee.com/src-openeuler/kernel)
 漏洞归属的版本：4.19.140,4.19.194,4.19.90,5.10.0,6.1.0,6.1.14,6.1.19,6.1.5,6.1.6,6.1.8,6.4.0,6.6.0
 CVSS V3.0分值：
  BaseScore：5.5 Medium
  Vector：CVSS：3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
 漏洞简述：
  In the Linux kernel, the following vulnerability has been resolved:PCI: rcar: Demote WARN() to dev_warn_ratelimited() in rcar_pcie_wakeup()Avoid large backtrace, it is sufficient to warn the user that there hasbeen a link problem. Either the link has failed and the system is in needof maintenance, or the link continues to work and user has been informed.The message from the warning can be looked up in the sources.This makes an actual link issue less verbose.First of all, this controller has a limitation in that the controllerdriver has to assist the hardware with transition to L1 link state bywriting L1IATN to PMCTRL register, the L1 and L0 link state switchingis not fully automatic on this controller.In case of an ASMedia ASM1062 PCIe SATA controller which does not supportASPM, on entry to suspend or during platform pm_test, the SATA controllerenters D3hot state and the link enters L1 state. If the SATA controllerwakes up before rcar_pcie_wakeup() was called and returns to D0, the linkreturns to L0 before the controller driver even started its transition toL1 link state. At this point, the SATA controller did send an PM_ENTER_L1DLLP to the PCIe controller and the PCIe controller received it, and thePCIe controller did set PMSR PMEL1RX bit.Once rcar_pcie_wakeup() is called, if the link is already back in L0 stateand PMEL1RX bit is set, the controller driver has no way to determine ifit should perform the link transition to L1 state, or treat the link as ifit is in L0 state. Currently the driver attempts to perform the transitionto L1 link state unconditionally, which in this specific case fails with aPMSR L1FAEG poll timeout, however the link still works as it is alreadyback in L0 state.Reduce this warning verbosity. In case the link is really broken, thercar_pcie_config_access() would fail, otherwise it will succeed and anysystem with this controller and ASM1062 can suspend without generatinga backtrace.
 漏洞公开时间：2024-08-21 09:15:11
 漏洞创建时间：2024-08-21 10:43:21
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2024-43876
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/2ae4769332dfdb97f4b6f5dc9ac8f46d02aaa3df |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/3ff3bdde950f1840df4030726cef156758a244d7 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/526a877c6273d4cd0d0aede84c1d620479764b1c |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/c93637e6a4c4e1d0e85ef7efac78d066bbb24d96 |  |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-43876 | https://bugzilla.suse.com/show_bug.cgi?id=1229485 |
| suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2024-43876 | https://bugzilla.suse.com/show_bug.cgi?id=1229485 |
| suse_bugzilla | https://git.kernel.org/stable/c/2ae4769332dfdb97f4b6f5dc9ac8f46d02aaa3df | https://bugzilla.suse.com/show_bug.cgi?id=1229485 |
| suse_bugzilla | https://git.kernel.org/stable/c/3ff3bdde950f1840df4030726cef156758a244d7 | https://bugzilla.suse.com/show_bug.cgi?id=1229485 |
| suse_bugzilla | https://git.kernel.org/stable/c/526a877c6273d4cd0d0aede84c1d620479764b1c | https://bugzilla.suse.com/show_bug.cgi?id=1229485 |
| suse_bugzilla | https://git.kernel.org/stable/c/c93637e6a4c4e1d0e85ef7efac78d066bbb24d96 | https://bugzilla.suse.com/show_bug.cgi?id=1229485 |
| suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-43876.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1229485 |
| ubuntu | https://www.cve.org/CVERecord?id=CVE-2024-43876 | https://ubuntu.com/security/CVE-2024-43876 |
| ubuntu | https://git.kernel.org/linus/c93637e6a4c4e1d0e85ef7efac78d066bbb24d96 (6.11-rc1) | https://ubuntu.com/security/CVE-2024-43876 |
| ubuntu | https://git.kernel.org/stable/c/2ae4769332dfdb97f4b6f5dc9ac8f46d02aaa3df | https://ubuntu.com/security/CVE-2024-43876 |
| ubuntu | https://git.kernel.org/stable/c/526a877c6273d4cd0d0aede84c1d620479764b1c | https://ubuntu.com/security/CVE-2024-43876 |
| ubuntu | https://git.kernel.org/stable/c/3ff3bdde950f1840df4030726cef156758a244d7 | https://ubuntu.com/security/CVE-2024-43876 |
| ubuntu | https://git.kernel.org/stable/c/c93637e6a4c4e1d0e85ef7efac78d066bbb24d96 | https://ubuntu.com/security/CVE-2024-43876 |
| ubuntu | https://nvd.nist.gov/vuln/detail/CVE-2024-43876 | https://ubuntu.com/security/CVE-2024-43876 |
| ubuntu | https://launchpad.net/bugs/cve/CVE-2024-43876 | https://ubuntu.com/security/CVE-2024-43876 |
| ubuntu | https://security-tracker.debian.org/tracker/CVE-2024-43876 | https://ubuntu.com/security/CVE-2024-43876 |
| debian |  | https://security-tracker.debian.org/tracker/CVE-2024-43876 |
| anolis |  | https://anas.openanolis.cn/cves/detail/CVE-2024-43876 |
| mageia |  | http://advisories.mageia.org/MGASA-2024-0309.html |
| amazon_linux_explore | https://access.redhat.com/security/cve/CVE-2024-43876 | https://explore.alas.aws.amazon.com/CVE-2024-43876.html |
| amazon_linux_explore | https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-43876 | https://explore.alas.aws.amazon.com/CVE-2024-43876.html |

</details>

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

| 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源  |
| ------- | -------- | ------- | -------- | --------- |
| linux |  | https://git.kernel.org/linus/c93637e6a4c4e1d0e85ef7efac78d066bbb24d96 | https://git.kernel.org/linus/84b576146294c2be702cfcd174eaa74167e276f9 | ubuntu |

</details>

二、漏洞分析结构反馈
 影响性分析说明：
  In the Linux kernel, the following vulnerability has been resolved:PCI: rcar: Demote WARN() to dev_warn_ratelimited() in rcar_pcie_wakeup()Avoid large backtrace, it is sufficient to warn the user that there hasbeen a link problem. Either the link has failed and the system is in needof maintenance, or the link continues to work and user has been informed.The message from the warning can be looked up in the sources.This makes an actual link issue less verbose.First of all, this controller has a limitation in that the controllerdriver has to assist the hardware with transition to L1 link state bywriting L1IATN to PMCTRL register, the L1 and L0 link state switchingis not fully automatic on this controller.In case of an ASMedia ASM1062 PCIe SATA controller which does not supportASPM, on entry to suspend or during platform pm_test, the SATA controllerenters D3hot state and the link enters L1 state. If the SATA controllerwakes up before rcar_pcie_wakeup() was called and returns to D0, the linkreturns to L0 before the controller driver even started its transition toL1 link state. At this point, the SATA controller did send an PM_ENTER_L1DLLP to the PCIe controller and the PCIe controller received it, and thePCIe controller did set PMSR PMEL1RX bit.Once rcar_pcie_wakeup() is called, if the link is already back in L0 stateand PMEL1RX bit is set, the controller driver has no way to determine ifit should perform the link transition to L1 state, or treat the link as ifit is in L0 state. Currently the driver attempts to perform the transitionto L1 link state unconditionally, which in this specific case fails with aPMSR L1FAEG poll timeout, however the link still works as it is alreadyback in L0 state.Reduce this warning verbosity. In case the link is really broken, thercar_pcie_config_access() would fail, otherwise it will succeed and anysystem with this controller and ASM1062 can suspend without generatinga backtrace.
 openEuler评分：
  5.5
 Vector：CVSS：3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
 受影响版本排查(受影响/不受影响)：
  1.openEuler-24.03-LTS(6.6.0):受影响
2.openEuler-20.03-LTS-SP4(4.19.90):不受影响
3.openEuler-22.03-LTS-SP3(5.10.0):不受影响
4.openEuler-22.03-LTS-SP4(5.10.0):不受影响
5.master(6.6.0):不受影响
6.openEuler-24.03-LTS-Next(6.6.0):不受影响
7.openEuler-24.03-LTS-SP1(6.6.0):不受影响

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

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

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

src-openEuler/kernel

内容风险标识

评论 (22)

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

内容风险标识

CVE-2024-43876

评论 (22)

搜索帮助

src-openEuler/kernel