SECUFOCUSNOW
Home›Remediation guides›CVE-2024-36894
CVE REMEDIATION GUIDE
Review reviewHighFixed-version data available

CVE-2024-36894 remediation guide

Linux Linux, linux_kernel, RUGGEDCOM RST2428P

In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_fs: Fix race between aio_cancel() and AIO request complete FFS based applications can utilize the aio_cancel() callback to dequeue pending USB requests submitted to the UDC. There is a scenario where the FFS application issues an AIO cancel call, while the UDC is handling a soft disconnect. For a DWC3 based implementation, the callstack looks like the following: DWC3 Gadget FFS Application dwc3_gadget_soft_disconnect() ... --> dwc3_stop_active_transfers() --> dwc3_gadget_giveback(-ESHUTDOWN) --> ffs_epfile_as...

Open CVE record
ProductLinux Linux, linux_kernel, RUGGEDCOM RST2428P
Affected versions>= 2e4c7553cd6f9c68bb741582dcb614edcbeca70f < f71a53148ce34898fef099b75386a3a9f4449311, >= 2e4c7553cd6f9c68bb741582dcb614edcbeca70f < 9e72ef59cbe61cd1243857a6418ca92104275867, >= 2e4c7553cd6f9c68bb741582dcb614edcbeca70f < e500b1c4e29ad0bd1c1332a1eaea2913627a92dd, >= 2e4c7553cd6f9c68bb741582dcb614edcbeca70f < 3613e5023f09b3308545e9d1acda86017ebd418a, >= 2e4c7553cd6f9c68bb741582dcb614edcbeca70f < a0fdccb1c9e027e3195f947f61aa87d6d0d2ea14, >= 2e4c7553cd6f9c68bb741582dcb614edcbeca70f < 73c05ad46bb4fbbdb346004651576d1c8dbcffbb, >= 2e4c7553cd6f9c68bb741582dcb614edcbeca70f < d7461830823242702f5d84084bcccb25159003f4, >= 2e4c7553cd6f9c68bb741582dcb614edcbeca70f < 24729b307eefcd7c476065cd7351c1a018082c19, >= 3.15, >= 2e4c7553cd6f < 73c05ad46bb4, >= 2e4c7553cd6f < d74618308232, >= 2e4c7553cd6f < 24729b307eef, >= 2e4c7553cd6f < f71a53148ce3, >= 2e4c7553cd6f < 9e72ef59cbe6, >= 2e4c7553cd6f < e500b1c4e29a, >= 2e4c7553cd6f < 3613e5023f09, >= 2e4c7553cd6f < a0fdccb1c9e0, >= 3.15 < 4.19.317, >= 4.20 < 5.4.279, >= 5.5 < 5.10.221
Fixed versions4.19.317, 5.4.279, 5.10.221, 5.15.162, 6.1.95, 6.6.31, 6.8.10
Priority basisReview · CVSS 7.8 · EPSS 0.19%
01

Identify the affected asset

Confirm whether Linux Linux, linux_kernel, RUGGEDCOM RST2428P 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.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= 2e4c7553cd6f9c68bb741582dcb614edcbeca70f < f71a53148ce34898fef099b75386a3a9f4449311, >= 2e4c7553cd6f9c68bb741582dcb614edcbeca70f < 9e72ef59cbe61cd1243857a6418ca92104275867, >= 2e4c7553cd6f9c68bb741582dcb614edcbeca70f < e500b1c4e29ad0bd1c1332a1eaea2913627a92dd, >= 2e4c7553cd6f9c68bb741582dcb614edcbeca70f < 3613e5023f09b3308545e9d1acda86017ebd418a, >= 2e4c7553cd6f9c68bb741582dcb614edcbeca70f < a0fdccb1c9e027e3195f947f61aa87d6d0d2ea14, >= 2e4c7553cd6f9c68bb741582dcb614edcbeca70f < 73c05ad46bb4fbbdb346004651576d1c8dbcffbb, >= 2e4c7553cd6f9c68bb741582dcb614edcbeca70f < d7461830823242702f5d84084bcccb25159003f4, >= 2e4c7553cd6f9c68bb741582dcb614edcbeca70f < 24729b307eefcd7c476065cd7351c1a018082c19, >= 3.15, >= 2e4c7553cd6f < 73c05ad46bb4, >= 2e4c7553cd6f < d74618308232, >= 2e4c7553cd6f < 24729b307eef, >= 2e4c7553cd6f < f71a53148ce3, >= 2e4c7553cd6f < 9e72ef59cbe6, >= 2e4c7553cd6f < e500b1c4e29a, >= 2e4c7553cd6f < 3613e5023f09, >= 2e4c7553cd6f < a0fdccb1c9e0, >= 3.15 < 4.19.317, >= 4.20 < 5.4.279, >= 5.5 < 5.10.221. Treat incomplete inventory results as unresolved.

03

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.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 4.19.317, 5.4.279, 5.10.221, 5.15.162, 6.1.95, 6.6.31, 6.8.10. Preserve configuration and rollback material before change.

05

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.