cbcvebase.
CVE-2024-47742
published 2024-10-21

CVE-2024-47742: In the Linux kernel, the following vulnerability has been resolved: firmware_loader: Block path traversal Most firmware names are hardcoded strings, or are…

PriorityP342high7.8CVSS 3.1
AVLACLPRLUINSUCHIHAH
EPSS
0.29%
20.6th percentile
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.

Affected

37 ranges· showing 25
VendorProductVersion rangeFixed in
debiandebian_linux
debianlinux< linux 6.1.115-1 (bookworm)linux 6.1.115-1 (bookworm)
debianlinux-6.1< linux 6.1.115-1 (bookworm)linux 6.1.115-1 (bookworm)
linuxlinux
linuxlinux>= abb139e75c2cdbb955e840d6331cb5863e409d0e < d1768e5535d3ded59f888637016e6f821f4e069fd1768e5535d3ded59f888637016e6f821f4e069f
linuxlinux>= abb139e75c2cdbb955e840d6331cb5863e409d0e < 9b1ca33ebd05b3acef5b976c04e5e791af93ce1b9b1ca33ebd05b3acef5b976c04e5e791af93ce1b
linuxlinux>= abb139e75c2cdbb955e840d6331cb5863e409d0e < c30558e6c5c9ad6c86459d9acce1520ceeab9ea6c30558e6c5c9ad6c86459d9acce1520ceeab9ea6
linuxlinux>= abb139e75c2cdbb955e840d6331cb5863e409d0e < a77fc4acfd49fc6076e565445b2bc5fdc3244da4a77fc4acfd49fc6076e565445b2bc5fdc3244da4
linuxlinux>= abb139e75c2cdbb955e840d6331cb5863e409d0e < 3d2411f4edcb649eaf232160db459bb4770b52513d2411f4edcb649eaf232160db459bb4770b5251
linuxlinux>= abb139e75c2cdbb955e840d6331cb5863e409d0e < 7420c1bf7fc784e587b87329cc6dfa3dca537aa47420c1bf7fc784e587b87329cc6dfa3dca537aa4
linuxlinux>= abb139e75c2cdbb955e840d6331cb5863e409d0e < 28f1cd94d3f1092728fb775a0fe26c5f1ac2ebeb28f1cd94d3f1092728fb775a0fe26c5f1ac2ebeb
linuxlinux>= abb139e75c2cdbb955e840d6331cb5863e409d0e < 6c4e13fdfcab34811c3143a0a03c05fec4e870ec6c4e13fdfcab34811c3143a0a03c05fec4e870ec
linuxlinux>= abb139e75c2cdbb955e840d6331cb5863e409d0e < f0e5311aa8022107d63c54e2f03684ec097d1394f0e5311aa8022107d63c54e2f03684ec097d1394
linuxlinux_kernel>= 0 < 5.10.234-15.10.234-1
linuxlinux_kernel>= 0 < 6.1.115-16.1.115-1
linuxlinux_kernel>= 0 < 6.11.2-16.11.2-1
linuxlinux_kernel>= 0 < 6.11.2-16.11.2-1
linuxlinux_kernel>= 0 < 5.4.0-208.2285.4.0-208.228
linuxlinux_kernel>= 0 < 5.15.0-127.1375.15.0-127.137
linuxlinux_kernel>= 0 < 6.8.0-54.566.8.0-54.56
linuxlinux_kernel>= 0 < 6.11.0-18.186.11.0-18.18
linuxlinux_kernel>= 3.7 < 4.19.3234.19.323
linuxlinux_kernel>= 4.20 < 5.4.2855.4.285
linuxlinux_kernel>= 5.11 < 5.15.1685.15.168
linuxlinux_kernel>= 5.16 < 6.1.1136.1.113

CVSS provenance

nvdv3.17.8HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
osv8.8HIGH
vendor_ubuntu8.8HIGH
vendor_debian7.8HIGH
vendor_msrc7.8HIGH
vendor_redhat7.8HIGH
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.