CVE-2024-49974: NFSD: Limit the number of concurrent async COPY operations
Noroxi assessment
Priority: Monitor (action score 22/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.27% (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 43e46ee5efc03990b223f7aa8b77aa9c3d3acfdf, 6a488ad7745b8f64625c6d3a24ce7e448e83f11b, 7ea9260874b779637aff6d24c344b8ef4ac862a0.
Low priority for now. Upgrade to Linux Linux 43e46ee5efc03990b223f7aa8b77aa9c3d3acfdf, 6a488ad7745b8f64625c6d3a24ce7e448e83f11b, 7ea9260874b779637aff6d24c344b8ef4ac862a0 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: NFSD: Limit the number of concurrent async COPY operations Nothing appears to limit the number of concurrent async COPY operations that clients can start. In addition, AFAICT each async COPY can copy an unlimited number of 4MB chunks, so can run for a long time. Thus IMO async COPY can become a DoS vector. Add a restriction mechanism that bounds the number of concurrent background COPY operations. Start simple and try to be fair -- this patch implements a per-namespace limit. An async COPY request that occurs while this limit is exceeded gets NFS4ERR_DELAY. The requesting client can choose to send the request again after a delay or fall back to a traditional read/write style copy. If there is need to make the mechanism more sophisticated, we can visit that in future patches.
- BDU:2025-04512
- DSA-5818-1
- SUSE-SU-2025:03636-1
- SUSE-SU-2025:03663-1
- SUSE-SU-2025:03671-1
- SUSE-SU-2025:20884-1
- SUSE-SU-2025:20886-1
- SUSE-SU-2025:20890-1
- SUSE-SU-2025:20891-1
- SUSE-SU-2025:20909-1
- SUSE-SU-2025:20920-1
- SUSE-SU-2025:3675-1
- SUSE-SU-2025:3704-1
- SUSE-SU-2025:3721-1
- SUSE-SU-2025:3734-1
- SUSE-SU-2025:3742-1
- Published
- Oct 21, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 19th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 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.
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
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 helpAffected 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 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 6.10.14
- linux linux kernel6.11 and later · before 6.11.3
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
- 4.20affected
- e0639dc5805a9d4faaa2c07ad98fa853b9529dd3 and later · before 9e52ff544e0bfa09ee339fd7b0937ee3c080c24eaffected · git
- e0639dc5805a9d4faaa2c07ad98fa853b9529dd3 and later · before 43e46ee5efc03990b223f7aa8b77aa9c3d3acfdfaffected · git
- e0639dc5805a9d4faaa2c07ad98fa853b9529dd3 and later · before 7ea9260874b779637aff6d24c344b8ef4ac862a0affected · git
- e0639dc5805a9d4faaa2c07ad98fa853b9529dd3 and later · before ae267989b7b7933dfedcd26468d0a88fc3a9da9eaffected · git
- e0639dc5805a9d4faaa2c07ad98fa853b9529dd3 and later · before b4e21431a0db4854b5023cd5af001be557e6c3dbaffected · git
- e0639dc5805a9d4faaa2c07ad98fa853b9529dd3 and later · before 6a488ad7745b8f64625c6d3a24ce7e448e83f11baffected · git
- e0639dc5805a9d4faaa2c07ad98fa853b9529dd3 and later · before aadc3bbea163b6caaaebfdd2b6c4667fbc726752affected · git
- before 4.20not affected · semver
- 5.10.231 and later · up to and including 5.10.*not affected · semver
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.119-1 | 6.1.119-1 |
| Debian:13 | linux | before 6.11.4-1 | 6.11.4-1 |
| SUSE:Linux Enterprise Live Patching 15 SP3 | kernel-livepatch-SLE15-SP3_Update_48 | before 19-150300.2.1 | 19-150300.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP3 | kernel-livepatch-SLE15-SP3_Update_49 | before 18-150300.2.1 | 18-150300.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_31 | before 17-150400.2.1 | 17-150400.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_32 | before 17-150400.2.1 | 17-150400.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP5 | kernel-livepatch-SLE15-SP5_Update_19 | before 17-150500.2.1 | 17-150500.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP5 | kernel-livepatch-SLE15-SP5_Update_20 | before 17-150500.2.1 | 17-150500.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_4 | before 19-150600.2.1 | 19-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6-RT_Update_3 | before 19-150600.2.1 | 19-150600.2.1 |
| SUSE:Linux Micro 6.0 | kernel-livepatch-MICRO-6-0_Update_2 | before 14-1.1 | 14-1.1 |
| SUSE:Linux Micro 6.0 | kernel-livepatch-MICRO-6-0_Update_3 | before 14-1.2 | 14-1.2 |
| SUSE:Linux Micro 6.0 | kernel-livepatch-MICRO-6-0-RT_Update_2 | before 14-1.1 | 14-1.1 |
| SUSE:Linux Micro 6.0 | kernel-livepatch-MICRO-6-0-RT_Update_3 | before 14-1.2 | 14-1.2 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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 KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-49971Oct 21, 2024 · drm/amd/display: Increase array size of dummy_boolean22Monitor
- ← EarlierCVE-2024-49972Oct 21, 2024 · drm/amd/display: Deallocate DML memory if allocation fails22Monitor
- Later →CVE-2024-49975Oct 21, 2024 · uprobes: fix kernel info leak via "[uprobes]" vma22Monitor
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 | 43e46ee5efc03990b223f7aa8b77aa9c3d3acfdf | Vendor (CNA) |
| Linux Linux | 6a488ad7745b8f64625c6d3a24ce7e448e83f11b | Vendor (CNA) |
| Linux Linux | 7ea9260874b779637aff6d24c344b8ef4ac862a0 | Vendor (CNA) |
| Linux Linux | 9e52ff544e0bfa09ee339fd7b0937ee3c080c24e | Vendor (CNA) |
| Linux Linux | aadc3bbea163b6caaaebfdd2b6c4667fbc726752 | Vendor (CNA) |
| Linux Linux | ae267989b7b7933dfedcd26468d0a88fc3a9da9e | Vendor (CNA) |
| Linux Linux | b4e21431a0db4854b5023cd5af001be557e6c3db | Vendor (CNA) |
| debian:linux | 6.1.119-1 · Debian:12 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0_Update_2 | 14-1.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0_Update_3 | 14-1.2 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0-RT_Update_2 | 14-1.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0-RT_Update_3 | 14-1.2 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP3_Update_48 | 19-150300.2.1 · SUSE:Linux Enterprise Live Patching 15 SP3 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP3_Update_49 | 18-150300.2.1 · SUSE:Linux Enterprise Live Patching 15 SP3 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP4_Update_31 | 17-150400.2.1 · SUSE:Linux Enterprise Live Patching 15 SP4 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP4_Update_32 | 17-150400.2.1 · SUSE:Linux Enterprise Live Patching 15 SP4 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP5_Update_19 | 17-150500.2.1 · SUSE:Linux Enterprise Live Patching 15 SP5 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP5_Update_20 | 17-150500.2.1 · SUSE:Linux Enterprise Live Patching 15 SP5 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP6_Update_4 | 19-150600.2.1 · SUSE:Linux Enterprise Live Patching 15 SP6 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP6-RT_Update_3 | 19-150600.2.1 · SUSE:Linux Enterprise Live Patching 15 SP6 | 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 researchersFinders, 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.
No nightly-computed relations.
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).
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
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/6a488ad7745b8f64625c6d3a24ce7e448e83f11b
- git.kernel.org/stable/c/7ea9260874b779637aff6d24c344b8ef4ac862a0
- git.kernel.org/stable/c/9e52ff544e0bfa09ee339fd7b0937ee3c080c24e
- git.kernel.org/stable/c/aadc3bbea163b6caaaebfdd2b6c4667fbc726752
- git.kernel.org/stable/c/ae267989b7b7933dfedcd26468d0a88fc3a9da9e
- git.kernel.org/stable/c/b4e21431a0db4854b5023cd5af001be557e6c3db
- lists.debian.org/debian-lts-announce/2025/01/msg00001.html
- lists.debian.org/debian-lts-announce/2025/03/msg00002.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.