CVE REMEDIATION GUIDE
Review reviewHighFixed-version data available

CVE-2024-49982 remediation guide

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: aoe: fix the potential use-after-free problem in more places For fixing CVE-2023-6270, f98364e92662 ("aoe: fix the potential use-after-free problem in aoecmd_cfg_pkts") makes tx() calling dev_put() instead of doing in aoecmd_cfg_pkts(). It avoids that the tx() runs into use-after-free. Then Nicolai Stange found more places in aoe have potential use-after-free problem with tx(). e.g. revalidate(), aoecmd_ata_rw(), resend(), probe() and aoecmd_cfg_rsp(). Those functions also use aoenet_xmit() to push packet to tx queue. So th...

Open CVE record
ProductLinux Linux, linux kernel
Affected versions>= ad80c34944d7175fa1f5c7a55066020002921a99 < 12f7b89dd72b25da4eeaa22097877963cad6418e, >= 1a54aa506b3b2f31496731039e49778f54eee881 < a786265aecf39015418e4f930cc1c14603a01490, >= faf0b4c5e00bb680e8e43ac936df24d3f48c8e65 < f63461af2c1a86af4217910e47a5c46e3372e645, >= 7dd09fa80b0765ce68bfae92f4e2f395ccf0fba4 < 07b418d50ccbbca7e5d87a3a0d41d436cefebf79, >= 74ca3ef68d2f449bc848c0a814cefc487bf755fa < bc2cbf7525ac288e07d465f5a1d8cb8fb9599254, >= eb48680b0255a9e8a9bdc93d6a55b11c31262e62 < acc5103a0a8c200a52af7d732c36a8477436a3d3, >= f98364e926626c678fb4b9004b75cacf92ff0662 < 89d9a69ae0c667e4d9d028028e2dcc837bae626f, >= f98364e926626c678fb4b9004b75cacf92ff0662 < 8253a60c89ec35c8f36fb2cc08cdf854c7a3eb58, >= f98364e926626c678fb4b9004b75cacf92ff0662 < 6d6e54fc71ad1ab0a87047fd9c211e75d86084a3, >= 079cba4f4e307c69878226fdf5228c20aa1c969c, >= a16fbb80064634b254520a46395e36b87ca4731e, >= 4.19.311 < 4.19.323, >= 5.4.273 < 5.4.285, >= 5.10.214 < 5.10.227, >= 5.15.153 < 5.15.168, >= 6.1.83 < 6.1.113, >= 6.6.23 < 6.6.55, >= 6.7.11 < 6.8, >= 6.8.2 < 6.9, >= 6.9
Fixed versions5.10.227, 5.15.168, 6.1.113, 6.6.55, 6.8.2, 6.10.14, 6.11.3
Priority basisReview · CVSS 7.8 · EPSS -
01

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.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= ad80c34944d7175fa1f5c7a55066020002921a99 < 12f7b89dd72b25da4eeaa22097877963cad6418e, >= 1a54aa506b3b2f31496731039e49778f54eee881 < a786265aecf39015418e4f930cc1c14603a01490, >= faf0b4c5e00bb680e8e43ac936df24d3f48c8e65 < f63461af2c1a86af4217910e47a5c46e3372e645, >= 7dd09fa80b0765ce68bfae92f4e2f395ccf0fba4 < 07b418d50ccbbca7e5d87a3a0d41d436cefebf79, >= 74ca3ef68d2f449bc848c0a814cefc487bf755fa < bc2cbf7525ac288e07d465f5a1d8cb8fb9599254, >= eb48680b0255a9e8a9bdc93d6a55b11c31262e62 < acc5103a0a8c200a52af7d732c36a8477436a3d3, >= f98364e926626c678fb4b9004b75cacf92ff0662 < 89d9a69ae0c667e4d9d028028e2dcc837bae626f, >= f98364e926626c678fb4b9004b75cacf92ff0662 < 8253a60c89ec35c8f36fb2cc08cdf854c7a3eb58, >= f98364e926626c678fb4b9004b75cacf92ff0662 < 6d6e54fc71ad1ab0a87047fd9c211e75d86084a3, >= 079cba4f4e307c69878226fdf5228c20aa1c969c, >= a16fbb80064634b254520a46395e36b87ca4731e, >= 4.19.311 < 4.19.323, >= 5.4.273 < 5.4.285, >= 5.10.214 < 5.10.227, >= 5.15.153 < 5.15.168, >= 6.1.83 < 6.1.113, >= 6.6.23 < 6.6.55, >= 6.7.11 < 6.8, >= 6.8.2 < 6.9, >= 6.9. 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: 5.10.227, 5.15.168, 6.1.113, 6.6.55, 6.8.2, 6.10.14, 6.11.3. 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.

CVE-2024-49982 Remediation Guide | SECUFOCUS NOW