NVD / CVE Program· CNA Linux

CVE-2024-47742: firmware_loader: Block path traversal

Noroxi assessment

Priority: Monitor (action score 31/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.28% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Linux Linux 28f1cd94d3f1092728fb775a0fe26c5f1ac2ebeb, 3d2411f4edcb649eaf232160db459bb4770b5251, 6c4e13fdfcab34811c3143a0a03c05fec4e870ec; Azure Linux 3.0 ARM 6.6.56.1-5; Azure Linux 3.0 x64 6.6.56.1-5.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 28f1cd94d3f1092728fb775a0fe26c5f1ac2ebeb, 3d2411f4edcb649eaf232160db459bb4770b5251, 6c4e13fdfcab34811c3143a0a03c05fec4e870ec; Azure Linux 3.0 ARM 6.6.56.1-5; Azure Linux 3.0 x64 6.6.56.1-5 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.8 · v3.1—No exploit Fix available

BDU:2025-03109

Published: Oct 21, 2024
Updated: Aug 5, 2026
EPSS: 0.2% · 21th percentile
CWE: CWE-22

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 7.8
CNA · Linux: 7.8; agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_kernel
debian	debian linux	cpe:2.3:o:debian:debian_linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

debian debian linux11.0
linux linux kernel3.7 and later · before 4.19.323
linux linux kernel4.20 and later · before 5.4.285
linux linux kernel5.5 and later · before 5.10.227
linux linux kernel5.11 and later · before 5.15.168
linux linux kernel5.16 and later · before 6.1.113
linux linux kernel6.2 and later · before 6.6.54
linux linux kernel6.7 and later · before 6.10.13
linux linux kernel6.11 and later · before 6.11.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

Linux Linux
- 3.7affected
- abb139e75c2cdbb955e840d6331cb5863e409d0e and later · before d1768e5535d3ded59f888637016e6f821f4e069faffected · git
- abb139e75c2cdbb955e840d6331cb5863e409d0e and later · before 9b1ca33ebd05b3acef5b976c04e5e791af93ce1baffected · git
- abb139e75c2cdbb955e840d6331cb5863e409d0e and later · before c30558e6c5c9ad6c86459d9acce1520ceeab9ea6affected · git
- abb139e75c2cdbb955e840d6331cb5863e409d0e and later · before a77fc4acfd49fc6076e565445b2bc5fdc3244da4affected · git
- abb139e75c2cdbb955e840d6331cb5863e409d0e and later · before 3d2411f4edcb649eaf232160db459bb4770b5251affected · git
- abb139e75c2cdbb955e840d6331cb5863e409d0e and later · before 7420c1bf7fc784e587b87329cc6dfa3dca537aa4affected · git
- abb139e75c2cdbb955e840d6331cb5863e409d0e and later · before 28f1cd94d3f1092728fb775a0fe26c5f1ac2ebebaffected · git
- abb139e75c2cdbb955e840d6331cb5863e409d0e and later · before 6c4e13fdfcab34811c3143a0a03c05fec4e870ecaffected · git
- abb139e75c2cdbb955e840d6331cb5863e409d0e and later · before f0e5311aa8022107d63c54e2f03684ec097d1394affected · git

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	linux	before 6.1.115-1	6.1.115-1
Debian:13	linux	before 6.11.2-1	6.11.2-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now

Published before and after this one in the same product

← EarlierCVE-2024-47740Oct 21, 2024 · f2fs: Require FMODE_WRITE for atomic write ioctls
22Monitor
← EarlierCVE-2024-47741Oct 21, 2024 · btrfs: fix race setting file private on concurrent lseek using same fd
28Monitor
Later →CVE-2024-47743Oct 21, 2024 · KEYS: prevent NULL pointer dereference in find_asymmetric_key()
22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Linux Linux	28f1cd94d3f1092728fb775a0fe26c5f1ac2ebeb	Vendor (CNA)
Linux Linux	3d2411f4edcb649eaf232160db459bb4770b5251	Vendor (CNA)
Linux Linux	6c4e13fdfcab34811c3143a0a03c05fec4e870ec	Vendor (CNA)
Linux Linux	7420c1bf7fc784e587b87329cc6dfa3dca537aa4	Vendor (CNA)
Linux Linux	9b1ca33ebd05b3acef5b976c04e5e791af93ce1b	Vendor (CNA)
Linux Linux	a77fc4acfd49fc6076e565445b2bc5fdc3244da4	Vendor (CNA)
Linux Linux	c30558e6c5c9ad6c86459d9acce1520ceeab9ea6	Vendor (CNA)
Linux Linux	d1768e5535d3ded59f888637016e6f821f4e069f	Vendor (CNA)
Linux Linux	f0e5311aa8022107d63c54e2f03684ec097d1394	Vendor (CNA)
Azure Linux 3.0 ARM	6.6.56.1-5 · kernel	Microsoft (MSRC)
Azure Linux 3.0 x64	6.6.56.1-5 · kernel	Microsoft (MSRC)
debian:linux	6.1.115-1 · Debian:12	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2023-52623209 days apartSUNRPC: Fix a suspicious RCU usage warning
22Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-24-1743 · Oct 22, 2024(Linux Kernel Güvenlik Bildirimi)

All national notices →

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

The bug in code

The whole CWE-22 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const file = path.join(ROOT, req.query.name);
2res.sendFile(file);

Fixed

1const file = path.resolve(ROOT, req.query.name);
2if (!file.startsWith(ROOT + path.sep)) {
3  return res.sendStatus(400);
4}
5res.sendFile(file);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

Fix✗ → ✓Sep 28, 2026, 10:09 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/28f1cd94d3f1092728fb775a0fe26c5f1ac2ebeb

Show all references (10 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records