Azure Linux 3.0 安全更新hyperv-daemons (CVE-2024-26935)

medium Nessus 插件 ID 295782

简介

远程 Azure Linux 主机缺少一个或多个安全更新。

描述

远程 Azure Linux 3.0 主机上安装的 hyperv-daemons 版本低于 测试的 版本。因此,该程序受到 CVE-2024-26935 公告中提及的一个漏洞影响。

- 已修复 Linux 内核中的下列漏洞:scsi: core: Fix unremoved procfs host directory regression Commit fc663711b944 (scsi: core: Remove the /proc/scsi/${proc_name} directory earlier) fixed a bug related to modules loading/unloading, by adding a call to scsi_proc_hostdir_rm() on scsi_remove_host(). But that led to a potential duplicate call to the hostdir_rm() routine, since it's also called from scsi_host_dev_release(). That triggered a regression report, which was then fixed by commit be03df3d4bfe (scsi: core: Fix a procfs host directory removal regression). The fix just dropped the hostdir_rm() call from dev_release(). But it happens that this proc directory is created on scsi_host_alloc(), and that function pairs with scsi_host_dev_release(), while scsi_remove_host() pairs with scsi_add_host(). In other words, it seems the reason for removing the proc directory on dev_release() was meant to cover cases in which a SCSI host structure was allocated, but the call to scsi_add_host() didn't happen. And that pattern happens to exist in some error paths, for example. Syzkaller causes that by using USB raw gadget device, error'ing on usb-storage driver, at usb_stor_probe2(). By checking that path, we can see that the BadDevice label leads to a scsi_host_put() after a SCSI host allocation, but there's no call to scsi_add_host() in such path. That leads to messages like this in dmesg (and a leak of the SCSI host proc structure): usb-storage 4-1:87.51: USB Mass Storage device detected proc_dir_entry 'scsi/usb-storage' already registered WARNING: CPU: 1 PID: 3519 at fs/proc/generic.c:377 proc_register+0x347/0x4e0 fs/proc/generic.c:376 The proper fix seems to still call scsi_proc_hostdir_rm() on dev_release(), but guard that with the state check for SHOST_CREATED; there is even a comment in scsi_host_dev_release() detailing that: such conditional is meant for cases where the SCSI host was allocated but there was no calls to {add,remove}_host(), like the usb-storage case. This is what we propose here and with that, the error path of usb-storage does not trigger the warning anymore.
(CVE-2024-26935)

请注意,Nessus 尚未测试此问题,而是只依据应用程序自我报告的版本号进行判断。

解决方案

更新受影响的程序包。

另见

https://nvd.nist.gov/vuln/detail/CVE-2024-26935

插件详情

严重性: Medium

ID: 295782

文件名: azure_linux_CVE-2024-26935.nasl

版本: 1.1

类型: local

发布时间: 2026/1/22

最近更新时间: 2026/1/22

支持的传感器: Nessus

风险信息

VPR

风险因素: Medium

分数: 4.4

CVSS v2

风险因素: Medium

基本分数: 4.6

时间分数: 3.4

矢量: CVSS2#AV:L/AC:L/Au:S/C:N/I:N/A:C

CVSS 分数来源: CVE-2024-26935

CVSS v3

风险因素: Medium

基本分数: 5.5

时间分数: 4.8

矢量: CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

时间矢量: CVSS:3.0/E:U/RL:O/RC:C

漏洞信息

CPE: p-cpe:/a:microsoft:azure_linux:hypervvssd, p-cpe:/a:microsoft:azure_linux:hyperv-tools, p-cpe:/a:microsoft:azure_linux:hyperv-daemons-debuginfo, p-cpe:/a:microsoft:azure_linux:hyperv-daemons-license, x-cpe:/o:microsoft:azure_linux, p-cpe:/a:microsoft:azure_linux:hypervfcopyd, p-cpe:/a:microsoft:azure_linux:hypervkvpd, p-cpe:/a:microsoft:azure_linux:hyperv-daemons

必需的 KB 项: Host/local_checks_enabled, Host/AzureLinux/release, Host/AzureLinux/rpm-list, Host/cpu

易利用性: No known exploits are available

补丁发布日期: 2024/9/10

漏洞发布日期: 2024/4/9

参考资料信息

CVE: CVE-2024-26935