CVE-2024-49874 remediation guide
Linux Linux, linux kernel
In the Linux kernel, the following vulnerability has been resolved: i3c: master: svc: Fix use after free vulnerability in svc_i3c_master Driver Due to Race Condition In the svc_i3c_master_probe function, &master->hj_work is bound with svc_i3c_master_hj_work, &master->ibi_work is bound with svc_i3c_master_ibi_work. And svc_i3c_master_ibi_work can start the hj_work, svc_i3c_master_irq_handler can start the ibi_work. If we remove the module which will call svc_i3c_master_remove to make cleanup, it will free master->base through i3c_master_unregister while the work mentioned above will be used....
Identify the affected asset
Confirm whether Linux Linux, linux kernel is installed, record the deployed version and installation path, and identify exposed interfaces.
- Record the product name, package or appliance identifier, and installed version.
- Identify internet-facing, administrative, API, and internal access paths.
- Preserve the pre-change configuration and relevant service logs.
Validate the affected-version match
Compare the deployed version with the affected range: >= 87e0f28eda36c7843523aa8dd0c5dab3331e9718 < 56bddf543d4d7ddeff3f87b554ddacfdf086bffe, >= 0f74f8b6675cc36d689abb4d9b3d75ab4049b7d7 < 4ac637122930cc4ab7e2c22e364cf3aaf96b05b1, >= 0f74f8b6675cc36d689abb4d9b3d75ab4049b7d7 < 4318998892bf8fe99f97bea18c37ae7b685af75a, >= 0f74f8b6675cc36d689abb4d9b3d75ab4049b7d7 < 27b55724d3f781dd6e635e89dc6e2fd78fa81a00, >= 0f74f8b6675cc36d689abb4d9b3d75ab4049b7d7 < 61850725779709369c7e907ae8c7c75dc7cec4f3, >= 6.4, >= 6.4 < 6.6.55, >= 6.7 < 6.10.14, >= 6.11 < 6.11.3. Treat incomplete inventory results as unresolved.
Prioritize with independent signals
The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.
Apply supported remediation
Follow the vendor advisory or supported update path. Current fixed-version status: 6.6.55, 6.10.14, 6.11.3. Preserve configuration and rollback material before change.
Verify the result
Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.
- Confirm the expected version and package state.
- Run a functional health check for critical service paths.
- Review authentication, error, application, and security monitoring logs.
- Reassess exposure if the supported fix cannot be applied.
Operational boundary
This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.