CVE - CVE-2024-47742

CVE-ID
CVE-2024-47742	Learn more at National Vulnerability Database (NVD) • CVSS Severity Rating • Fix Information • Vulnerable Software Versions • SCAP Mappings • CPE Information
Description
In the Linux kernel, the following vulnerability has been resolved: firmware_loader: Block path traversal Most firmware names are hardcoded strings, or are constructed from fairly constrained format strings where the dynamic parts are just some hex numbers or such. However, there are a couple codepaths in the kernel where firmware file names contain string components that are passed through from a device or semi-privileged userspace; the ones I could find (not counting interfaces that require root privileges) are: - lpfc_sli4_request_firmware_update() seems to construct the firmware filename from "ModelName", a string that was previously parsed out of some descriptor ("Vital Product Data") in lpfc_fill_vpd() - nfp_net_fw_find() seems to construct a firmware filename from a model name coming from nfp_hwinfo_lookup(pf->hwinfo, "nffw.partno"), which I think parses some descriptor that was read from the device. (But this case likely isn't exploitable because the format string looks like "netronome/nic_%s", and there shouldn't be any folders starting with "netronome/nic_". The previous case was different because there, the "%s" is at the start of the format string.) - module_flash_fw_schedule() is reachable from the ETHTOOL_MSG_MODULE_FW_FLASH_ACT netlink command, which is marked as GENL_UNS_ADMIN_PERM (meaning CAP_NET_ADMIN inside a user namespace is enough to pass the privilege check), and takes a userspace-provided firmware name. (But I think to reach this case, you need to have CAP_NET_ADMIN over a network namespace that a special kind of ethernet device is mapped into, so I think this is not a viable attack path in practice.) Fix it by rejecting any firmware names containing ".." path components. For what it's worth, I went looking and haven't found any USB device drivers that use the firmware loader dangerously.
References
Note: References are provided for the convenience of the reader to help distinguish between vulnerabilities. The list is not intended to be complete.
MISC:https://git.kernel.org/stable/c/28f1cd94d3f1092728fb775a0fe26c5f1ac2ebeb URL:https://git.kernel.org/stable/c/28f1cd94d3f1092728fb775a0fe26c5f1ac2ebeb MISC:https://git.kernel.org/stable/c/3d2411f4edcb649eaf232160db459bb4770b5251 URL:https://git.kernel.org/stable/c/3d2411f4edcb649eaf232160db459bb4770b5251 MISC:https://git.kernel.org/stable/c/6c4e13fdfcab34811c3143a0a03c05fec4e870ec URL:https://git.kernel.org/stable/c/6c4e13fdfcab34811c3143a0a03c05fec4e870ec MISC:https://git.kernel.org/stable/c/7420c1bf7fc784e587b87329cc6dfa3dca537aa4 URL:https://git.kernel.org/stable/c/7420c1bf7fc784e587b87329cc6dfa3dca537aa4 MISC:https://git.kernel.org/stable/c/9b1ca33ebd05b3acef5b976c04e5e791af93ce1b URL:https://git.kernel.org/stable/c/9b1ca33ebd05b3acef5b976c04e5e791af93ce1b MISC:https://git.kernel.org/stable/c/a77fc4acfd49fc6076e565445b2bc5fdc3244da4 URL:https://git.kernel.org/stable/c/a77fc4acfd49fc6076e565445b2bc5fdc3244da4 MISC:https://git.kernel.org/stable/c/c30558e6c5c9ad6c86459d9acce1520ceeab9ea6 URL:https://git.kernel.org/stable/c/c30558e6c5c9ad6c86459d9acce1520ceeab9ea6 MISC:https://git.kernel.org/stable/c/d1768e5535d3ded59f888637016e6f821f4e069f URL:https://git.kernel.org/stable/c/d1768e5535d3ded59f888637016e6f821f4e069f MISC:https://git.kernel.org/stable/c/f0e5311aa8022107d63c54e2f03684ec097d1394 URL:https://git.kernel.org/stable/c/f0e5311aa8022107d63c54e2f03684ec097d1394
Assigning CNA
kernel.org
Date Record Created
20240930	Disclaimer: The record creation date may reflect when the CVE ID was allocated or reserved, and does not necessarily indicate when this vulnerability was discovered, shared with the affected vendor, publicly disclosed, or updated in CVE.
Phase (Legacy)
Assigned (20240930)
Votes (Legacy)

Comments (Legacy)

Proposed (Legacy)
N/A
This is an record on the CVE List, which provides common identifiers for publicly known cybersecurity vulnerabilities.
Search CVE Using Keywords: You can also search by reference using the CVE Reference Maps.
For More Information: CVE Request Web Form (select "Other" from dropdown)