CVE REMEDIATION GUIDE
CISA KEV · Known exploitedHighFixed-version data available

CVE-2024-1086 remediation guide

Linux Kernel

A use-after-free vulnerability in the Linux kernel's netfilter: nf_tables component can be exploited to achieve local privilege escalation. The nft_verdict_init() function allows positive values as drop error within the hook verdict, and hence the nf_hook_slow() function can cause a double free vulnerability when NF_DROP is issued with a drop error which resembles NF_ACCEPT. We recommend upgrading past commit f342de4e2f33e0e39165d8639387aa6c19dff660.

Open CVE record
ProductLinux Kernel
Affected versions3.15, >= 3.15 < 5.15.149, >= 6.1 < 6.1.76, >= 6.2 < 6.6.15, >= 6.7 < 6.7.3, 6.8, 39, 7.0, 7.0 s390x, 7.0 ppc64, 7.0 ppc64le, 10.0
Fixed versions5.15.149, 6.1.76, 6.6.15, 6.7.3
Priority basisImmediate · CVSS 7.8 · EPSS 28.1%
01

Identify the affected asset

Confirm whether 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: 3.15, >= 3.15 < 5.15.149, >= 6.1 < 6.1.76, >= 6.2 < 6.6.15, >= 6.7 < 6.7.3, 6.8, 39, 7.0, 7.0 s390x, 7.0 ppc64, 7.0 ppc64le, 10.0. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

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.