CVE-2024-47742
Last modified
CVE-2024-47742 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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.. EPSS estimates a 0.29% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Debian | Debian Linux | 11.0 |
| Linux | Linux Kernel | >= 3.7, < 4.19.323 |
| Linux | Linux Kernel | >= 4.20, < 5.4.285 |
| Linux | Linux Kernel | >= 5.5, < 5.10.227 |
| Linux | Linux Kernel | >= 5.11, < 5.15.168 |
| Linux | Linux Kernel | >= 5.16, < 6.1.113 |
| Linux | Linux Kernel | >= 6.2, < 6.6.54 |
| Linux | Linux Kernel | >= 6.7, < 6.10.13 |
| Linux | Linux Kernel | >= 6.11, < 6.11.2 |
References
- https://lists.debian.org/debian-lts-announce/2025/01/msg00001.htmlMailing List, Third Party Advisory
- https://lists.debian.org/debian-lts-announce/2025/03/msg00002.htmlMailing List, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2024-47742?
How severe is CVE-2024-47742?
How do I fix CVE-2024-47742?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2024
- CVE-2024-47737In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-47738In the Linux kernel, the following vulnerability has been re…3.3
- CVE-2024-47739In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-4774The `ShmemCharMapHashEntry()` code was susceptible to potent…6.5
- CVE-2024-47740In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-47741In the Linux kernel, the following vulnerability has been re…7
- CVE-2024-47743In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-47744In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-47745In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-47746In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-47747In the Linux kernel, the following vulnerability has been re…7
- CVE-2024-47748In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2024-47742?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
