Service interruption via leaked inode reference
Published Dec 27, 2024 · Updated May 11, 2026
Resource leak in Linux kernel OCFS2 allows local users to cause a service interrupt through a failed inode initialization path. When new_inode() succeeds but dquot_initialize() fails, ocfs2_get_init_inode() returns without calling iput(), leaving a busy inode after unmount. Reaching the error path requires local low-privileged access to an OCFS2 filesystem; the documented consequence is unreleased inode state and availability loss.
Summary
What happened
Resource leak in Linux kernel OCFS2 allows local users to cause a service interrupt through a failed inode initialization path. When new_inode() succeeds but dquot_initialize() fails, ocfs2_get_init_inode() returns without calling iput(), leaving a busy inode after unmount. Reaching the error path requires local low-privileged access to an OCFS2 filesystem; the documented consequence is unreleased inode state and availability loss.
The record
- CVE
- CVE-2024-56630
- Published
- Dec 27, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-908, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 27, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 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=4.3
- Affected versionversion=9c89fe0af826bfff36d8019ea6fd78db09b3c478 <03db61c43c8e2729896fda6b9a95c7fb5c875c20
- Affected versionversion=9c89fe0af826bfff36d8019ea6fd78db09b3c478 <67c2c6d0564ca05348ba4f8f6eaf7a0713f56c15
- Affected versionversion=9c89fe0af826bfff36d8019ea6fd78db09b3c478 <911fcc95b530615b484e8920741fc5e4bc4e684a
- Affected versionversion=9c89fe0af826bfff36d8019ea6fd78db09b3c478 <965b5dd1894f4525f38c1b5f99b0106a07dbb5db
- Affected versionversion=9c89fe0af826bfff36d8019ea6fd78db09b3c478 <9c19ea59965ebb482e227532f7bbb01792fb028c
- Affected versionversion=9c89fe0af826bfff36d8019ea6fd78db09b3c478 <a84d507d3290aca249b44ae992af9e10590cc5f6
- Affected versionversion=9c89fe0af826bfff36d8019ea6fd78db09b3c478 <c5327720a4655303ffa3f632d86ee205dd783f32
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