NFS lock failure via transient reference count
Published Mar 13, 2024 · Updated May 23, 2026
Incorrect status handling in Linux NFSD allows attackers to disrupt NFSv4 lock-owner state through concurrent LOCK and RELEASE requests. nfsd4_release_lockowner() compares the transient so_count reference total with two and returns NFS4ERR_LOCKS_HELD even when no locks remain. Reachability requires NFSv4 request access; reuse of the retained owner with sequence zero produces NFS4ERR_BAD_SEQID and prevents correct locking.
Summary
What happened
Incorrect status handling in Linux NFSD allows attackers to disrupt NFSv4 lock-owner state through concurrent LOCK and RELEASE requests. nfsd4_release_lockowner() compares the transient so_count reference total with two and returns NFS4ERR_LOCKS_HELD even when no locks remain. Reachability requires NFSv4 request access; reuse of the retained owner with sequence zero produces NFS4ERR_BAD_SEQID and prevents correct locking.
The record
- CVE
- CVE-2024-26629
- Published
- Mar 13, 2024
- Updated
- May 23, 2026
- Vendor
- Siemens
- Product
- SIMATIC S7-1500 TM MFP - GNU/Linux subsystem
- Classifications
- CWE-393, T1499
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Mar 13, 2024CVE publishedPublication date reported by the CVE source.
- May 23, 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=0 <*
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.
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