Remote NFS hang via recursive tmpfs inode lock
Published Dec 4, 2024 · Updated Aug 5, 2026
Deadlock in affected Linux kernel releases allows remote attackers to hang NFS service access via metadata operations on an exported tmpfs. The shmem_getattr() path takes the inode read lock while NFS metadata handlers already hold the same inode lock for writing, causing a recursive rwsem deadlock. Exposure requires a tmpfs filesystem exported through NFS; a single unauthenticated CREATE or SETATTR request can hang the server.
Summary
What happened
Deadlock in affected Linux kernel releases allows remote attackers to hang NFS service access via metadata operations on an exported tmpfs. The shmem_getattr() path takes the inode read lock while NFS metadata handlers already hold the same inode lock for writing, causing a recursive rwsem deadlock. Exposure requires a tmpfs filesystem exported through NFS; a single unauthenticated CREATE or SETATTR request can hang the server.
The record
- CVE
- CVE-2024-53136
- Published
- Dec 4, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-362, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 4, 2024CVE 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=3d9528484480e8f4979b3a347930ed383be99f89 <d3f9d88c2c03b2646ace336236adca19f7697bd3
- Affected versionversion=4.19.323 <4.19.325
- Affected versionversion=5.10.229 <5.10.231
- Affected versionversion=5.15.171 <5.15.174
- Affected versionversion=5.4.285 <5.4.287
- Affected versionversion=6.1.116 <6.1.119
- Affected versionversion=6.11.7 <6.11.10
- Affected versionversion=6.6.60 <6.6.63
- Affected versionversion=7cc30ada84323be19395094d567579536e0d187e <a3c65022d89d5baa2cea8e87a6de983ea305f14c
- Affected versionversion=82cae1e30bd940253593c2d4f16d88343d1358f4 <5874c1150e77296565ad6e495ef41fbf87570d14
- Affected versionversion=9fb9703cd43ee20a6de8ccdef991677b7274cec0 <36b537e8f302f670c7cf35d88a3a294443e32d52
- Affected versionversion=bda1a99a0dd644f31a87d636ac624eeb975cb65a <57cc8d253099d1b8627f0fb487ee011d9158ccc9
- Affected versionversion=d949d1d14fa281ace388b1de978e8f2cd52875cf <d1aa0c04294e29883d65eac6c2f72fe95cc7c049
- Affected versionversion=edd1f905050686fdc4cfe233d818469fdf7d5ff8 <64e67e8694252c1bf01b802ee911be3fee62c36b
- Affected versionversion=ffd56612566bc23877c8f45def2801f3324a222a <901dc2ad7c3789fa87dc3956f6697c5d62d5cf7e
What conditions does exploitation require?
What is affected?
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