Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-47742firmware_loader: Block path traversal

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.

Timeline

  1. ID reserved

    By Linux

  2. · 21 days later

    Published

  3. · 22 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-47742, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.29% · top 78% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected abb139e75c2cdbb955e840d6331cb5863e409d0e – < d1768e5535d3ded59f888637016e6f821f4e069f
    • affected abb139e75c2cdbb955e840d6331cb5863e409d0e – < 9b1ca33ebd05b3acef5b976c04e5e791af93ce1b
    • affected abb139e75c2cdbb955e840d6331cb5863e409d0e – < c30558e6c5c9ad6c86459d9acce1520ceeab9ea6
    • affected abb139e75c2cdbb955e840d6331cb5863e409d0e – < a77fc4acfd49fc6076e565445b2bc5fdc3244da4
    • affected abb139e75c2cdbb955e840d6331cb5863e409d0e – < 3d2411f4edcb649eaf232160db459bb4770b5251
    • affected abb139e75c2cdbb955e840d6331cb5863e409d0e – < 7420c1bf7fc784e587b87329cc6dfa3dca537aa4
    • affected abb139e75c2cdbb955e840d6331cb5863e409d0e – < 28f1cd94d3f1092728fb775a0fe26c5f1ac2ebeb
    • affected abb139e75c2cdbb955e840d6331cb5863e409d0e – < 6c4e13fdfcab34811c3143a0a03c05fec4e870ec
    • affected abb139e75c2cdbb955e840d6331cb5863e409d0e – < f0e5311aa8022107d63c54e2f03684ec097d1394
  • Linux · Linux

    • affected 3.7
    • unaffected < 3.7
    • unaffected 4.19.323 – ≤ 4.19.*
    • unaffected 5.4.285 – ≤ 5.4.*
    • unaffected 5.10.227 – ≤ 5.10.*
    • unaffected 5.15.168 – ≤ 5.15.*
    • unaffected 6.1.113 – ≤ 6.1.*
    • unaffected 6.6.54 – ≤ 6.6.*
    • unaffected 6.10.13 – ≤ 6.10.*
    • unaffected 6.11.2 – ≤ 6.11.*
    • unaffected 6.12 – ≤ *

References

References11

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-47742 badge
[![CVE-2024-47742](https://cveledger.app/badge/CVE-2024-47742.svg)](https://cveledger.app/cve/CVE-2024-47742)

Record last updated .