CVE-2024-49966: ocfs2: cancel dqi_sync_work before freeing oinfo
In the Linux kernel, the following vulnerability has been resolved:
ocfs2: cancel dqi_sync_work before freeing oinfo
ocfs2_global_read_info() will initialize and schedule dqi_sync_work at the
end, if error occurs after successfully reading global quota, it will
trigger the following warning with CONFIG_DEBUG_OBJECTS_* enabled:
ODEBUG: free active (active state 0) object: 00000000d8b0ce28 object type: timer_list hint: qsync_work_fn+0x0/0x16c
This reports that there is an active delayed work when freeing oinfo in
error handling, so cancel dqi_sync_work first. BTW, return status instead
of -1 when .read_file_info fails.
Security readout for executives and security teams
Plain-English summary
A Linux OCFS2 quota error path can free filesystem quota state while scheduled work is still active. That race may corrupt kernel memory, potentially affecting confidentiality, integrity, or availability. The supplied CVSS score is 7.8, but exposure depends on using OCFS2 global quotas and reaching the affected error path.
Executive priority
Prioritize systems using OCFS2 global quotas, especially multi-user or sensitive clustered storage. Patch through normal emergency kernel procedures after compatibility testing. Systems not using OCFS2 have substantially lower likely exposure, but inventory evidence should support that conclusion.
Technical view
After ocfs2_global_read_info() schedules dqi_sync_work, a later read failure can free oinfo without first cancelling that delayed work. The worker may then access released kernel memory. The referenced kernel fix cancels the work before cleanup and preserves the read_file_info() error status.
Likely exposure
Likely limited to Linux systems running an affected kernel with OCFS2 and global quota handling in use. The supplied record lists affected versions from 2.6.29 through several stable releases, including 6.12, but does not provide reliable fixed-version boundaries.
Exploitation context
The CVSS vector describes local, low-privilege exploitation without user interaction. However, the source bundle provides no proof of practical exploitation, public weaponization, or active attacks, and the CVE is not listed as KEV.
Researcher notes
The supplied description demonstrates an active delayed-work object surviving into oinfo cleanup, consistent with a potential use-after-free condition. Debug-object warnings establish faulty lifecycle handling, not exploitability. Exact triggering conditions, affected configuration boundaries, and fixed package versions require vendor-specific confirmation.
Mitigation direction
Identify systems running OCFS2 and determine whether global quotas are enabled.
Map installed kernel packages against vendor advisories for CVE-2024-49966.
Apply a vendor-supported kernel containing the referenced upstream fix.
Reboot affected systems when required to activate the updated kernel.
Consult vendor guidance for temporary controls if immediate kernel updates are unavailable.
Validation and detection
Confirm the running kernel, not only the installed package, includes the fix.
Verify vendor changelogs reference CVE-2024-49966 or the applicable stable-kernel commit.
Review kernel logs for active-object warnings involving qsync_work_fn or OCFS2 quota initialization.
Test OCFS2 quota initialization and failure handling in a controlled non-production environment.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-49966 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.