CVE-2026-99550
Severity unknownNo known exploitationFix availableocfs2: pin owning modules for open debugfs files
Record last updated
CVSS score
No score published yet
EPSS, chance of exploitation in 30 days
Higher than 5% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
Description
In the Linux kernel, the following vulnerability has been resolved: ocfs2: pin owning modules for open debugfs files The OCFS2 debugfs file operation tables do not set owner. The full debugfs proxy obtains real_fops with fops_get() at open and keeps it until final release. Without an owner, this does not acquire a reference to the module containing the table and its callbacks. Removing the debugfs entries does not drain retained open files. An open connected_nodes file can therefore outlive ocfs2_nodemanager and make full_proxy_release() read real_fops->release from freed module memory. Heming also reproduced the issue with fs_state and asked for the other OCFS2 debugfs operation tables to be checked. Set owner to THIS_MODULE in all eleven explicit debugfs operation tables: five in ocfs2_nodemanager, four in ocfs2_dlm, and two in ocfs2. The existing debugfs get/put pair then holds the appropriate module until final release. Leave the open, read and release callbacks unchanged. The blockcheck table already sets owner through DEFINE_DEBUGFS_ATTRIBUTE(), so it needs no change. The original controlled test used an unloadable OCFS2 module and case-local probe filters without changing the candidate open, unload or release logic. Closing a retained connected_nodes file after normal unload produced: BUG: unable to handle page fault for address: fffffbfff804cfef Oops: Oops: 0000 [#1] SMP KASAN NOPTI RIP: 0010:full_proxy_release+0xbf/0x190 Call Trace: __fput+0x39a/0xa60 fput_close_sync+0xff/0x200 __x64_sys_close+0x8c/0xf0 do_syscall_64+0x114/0x620 entry_SYSCALL_64_after_hwframe+0x77/0x7f Modules linked in: [last unloaded: ocfs2_nodemanager]
Patching and mitigation
- Patch status
- Fix available (source: CVE record (Linux))
- Fix documented (source date)
- Mitigation
- None documented
- Vendor guidance
- No vendor link on record
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Linux | Linux | from ccd979bdbce9fba8412beb3f1de68a9d0171b12c before f5e973e238ba686a17f19dfbccccdd1c4447a2be | f5e973e238ba686a17f19dfbccccdd1c4447a2be | CVE Program |
| Linux | Linux | from ccd979bdbce9fba8412beb3f1de68a9d0171b12c before 625bbfa9c160ca9d4128acddb15fd7da3ea66c17 | 625bbfa9c160ca9d4128acddb15fd7da3ea66c17 | CVE Program |
| Linux | Linux | from ccd979bdbce9fba8412beb3f1de68a9d0171b12c before 26d7e34b4226709084461a07bf28d9066fa96d8c | 26d7e34b4226709084461a07bf28d9066fa96d8c | CVE Program |
| Linux | Linux | from ccd979bdbce9fba8412beb3f1de68a9d0171b12c before ae5ea8ca2db9a0306c04f4777433908456ce8541 | ae5ea8ca2db9a0306c04f4777433908456ce8541 | CVE Program |
| Linux | Linux | 2.6.16 | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.12.117 up to and including 6.12.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.18.61 up to and including 6.18.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 7.3.2 up to and including 7.3.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | 7.4-rc1 | Not documented | CVE Program |
| Linux | Linux (unaffected) | all versions before 2.6.16 | Not documented | CVE Program |
Timeline
Disclosure
CVE record published by Linux
Source: CVE Program (opens in a new tab)
Patch
Fix documented by CVE record (Linux)
Vendor guidance and references
- https://git.kernel.org/stable/c/26d7e34b4226709084461a07bf28d9066fa96d8c (opens in a new tab)
- https://git.kernel.org/stable/c/625bbfa9c160ca9d4128acddb15fd7da3ea66c17 (opens in a new tab)
- https://git.kernel.org/stable/c/ae5ea8ca2db9a0306c04f4777433908456ce8541 (opens in a new tab)
- https://git.kernel.org/stable/c/f5e973e238ba686a17f19dfbccccdd1c4447a2be (opens in a new tab)