CVE-2022-48744 remediation guide

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Avoid field-overflowing memcpy() In preparation for FORTIFY_SOURCE performing compile-time and run-time field bounds checking for memcpy(), memmove(), and memset(), avoid intentionally writing across neighboring fields. Use flexible arrays instead of zero-element arrays (which look like they are always overflowing) and split the cross-field memcpy() into two halves that can be appropriately bounds-checked by the compiler. We were doing: #define ETH_HLEN 14 #define VLAN_HLEN 4 ... #define MLX5E_XDP_MIN_INLINE (ETH...

Open CVE record

ProductLinux Linux, linux kernel

Affected versions>= b5503b994ed5ed8dbfe821317e7b5b38acb065c5 < 49bcbe531f79fc35bb10020f7695f9f01e4f0ca8, >= b5503b994ed5ed8dbfe821317e7b5b38acb065c5 < 8fbdf8c8b8ab82beab882175157650452c46493e, >= b5503b994ed5ed8dbfe821317e7b5b38acb065c5 < ad5185735f7dab342fdd0dd41044da4c9ccfef67, >= 4.9, >= 4.9 < 5.10.248, >= 5.11 < 5.16.6, 5.17

Fixed versions5.10.248, 5.16.6

Priority basisReview · CVSS 7.8 · EPSS 0.61%

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: >= b5503b994ed5ed8dbfe821317e7b5b38acb065c5 < 49bcbe531f79fc35bb10020f7695f9f01e4f0ca8, >= b5503b994ed5ed8dbfe821317e7b5b38acb065c5 < 8fbdf8c8b8ab82beab882175157650452c46493e, >= b5503b994ed5ed8dbfe821317e7b5b38acb065c5 < ad5185735f7dab342fdd0dd41044da4c9ccfef67, >= 4.9, >= 4.9 < 5.10.248, >= 5.11 < 5.16.6, 5.17. 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: 5.10.248, 5.16.6. 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.