Remote service interruption via concurrent OPEN memory leak
Published Jan 8, 2025 · Updated Aug 5, 2026
Memory leak in Linux kernel nfsd allows remote attackers to exhaust kernel memory through concurrent NFSv4 OPEN requests. find_or_alloc_open_stateowner removes an unconfirmed owner from lookup visibility while another nfsd thread can still attach state, leaving associated kernel objects unreachable. The race requires concurrent requests for the same fresh open owner from an NFS client allowed by the export; repeated wins can prevent unmounting or crash the server.
Summary
What happened
Memory leak in Linux kernel nfsd allows remote attackers to exhaust kernel memory through concurrent NFSv4 OPEN requests. find_or_alloc_open_stateowner removes an unconfirmed owner from lookup visibility while another nfsd thread can still attach state, leaving associated kernel objects unreachable. The race requires concurrent requests for the same fresh open owner from an NFS client allowed by the export; repeated wins can prevent unmounting or crash the server.
The record
- CVE
- CVE-2024-56779
- Published
- Jan 8, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 8, 2025CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.17
- Affected versionversion=3234975f477f746c22d076ea178a79ea104b2ca7 <0ab0a3ad24e970e894abcac58f85c332d1726749
- Affected versionversion=3234975f477f746c22d076ea178a79ea104b2ca7 <2d505a801e57428057563762f67a5a62009b2600
- Affected versionversion=3234975f477f746c22d076ea178a79ea104b2ca7 <37dfc81266d3a32294524bfadd3396614f8633ee
- Affected versionversion=3234975f477f746c22d076ea178a79ea104b2ca7 <45abb68c941ebc9a35c6d3a7b08196712093c636
- Affected versionversion=3234975f477f746c22d076ea178a79ea104b2ca7 <6f73f920b7ad0084373e46121d7ac34117aed652
- Affected versionversion=3234975f477f746c22d076ea178a79ea104b2ca7 <98100e88dd8865999dc6379a3356cd799795fe7b
- Affected versionversion=3234975f477f746c22d076ea178a79ea104b2ca7 <a85364f0d30dee01c5d5b4afa55a9629a8f36d8e
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo