Remote kernel compromise via stale plock callback
Published Feb 26, 2025 · Updated Aug 5, 2026
Out-of-bounds read in Linux kernel DLM plock handling allows remote attackers to disclose memory or execute code via NFS unlocks. dev_write() treats each recv_list entry as struct plock_xop and reads its callback field even when dlm_posix_unlock allocated only the smaller struct plock_op. A remote NFS client can reach the path through lock operations on a writable exported GFS2 or OCFS2 share; a groomed stale callback can disclose memory, crash the kernel, or redirect execution.
Summary
What happened
Out-of-bounds read in Linux kernel DLM plock handling allows remote attackers to disclose memory or execute code via NFS unlocks. dev_write() treats each recv_list entry as struct plock_xop and reads its callback field even when dlm_posix_unlock allocated only the smaller struct plock_op. A remote NFS client can reach the path through lock operations on a writable exported GFS2 or OCFS2 share; a groomed stale callback can disclose memory, crash the kernel, or redirect execution.
The record
- CVE
- CVE-2022-49407
- Published
- Feb 26, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-125, T1210
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 26, 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=2.6.22
- Affected versionversion=586759f03e2e9031ac5589912a51a909ed53c30a <2c55155cc365861044d9e6e80e342693e8805e33
- Affected versionversion=586759f03e2e9031ac5589912a51a909ed53c30a <42252d0d2aa9b94d168241710a761588b3959019
- Affected versionversion=586759f03e2e9031ac5589912a51a909ed53c30a <49cd9eb7b9a7b88124b31e31f8e539acaf1b3a6d
- Affected versionversion=586759f03e2e9031ac5589912a51a909ed53c30a <56aa8d1fbd02357f3bf81bdfba1cde87ce8402fc
- Affected versionversion=586759f03e2e9031ac5589912a51a909ed53c30a <5a1765adf9855cf0f6d3f7e0eb4b78ca66f70dee
- Affected versionversion=586759f03e2e9031ac5589912a51a909ed53c30a <72f2f68970f9bdc252d59e119b385a6441b0b155
- Affected versionversion=586759f03e2e9031ac5589912a51a909ed53c30a <899bc4429174861122f0c236588700a4710c1fec
- Affected versionversion=586759f03e2e9031ac5589912a51a909ed53c30a <acdad5bc9827922ec2f2e84fd198718aa8e8ab92
- Affected versionversion=586759f03e2e9031ac5589912a51a909ed53c30a <e421872fa17542cf33747071fb141b0130ce9ef7
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