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

CVE-2024-36883 remediation guide

Linux Linux, linux kernel, debian linux

In the Linux kernel, the following vulnerability has been resolved: net: fix out-of-bounds access in ops_init net_alloc_generic is called by net_alloc, which is called without any locking. It reads max_gen_ptrs, which is changed under pernet_ops_rwsem. It is read twice, first to allocate an array, then to set s.len, which is later used to limit the bounds of the array access. It is possible that the array is allocated and another thread is registering a new pernet ops, increments max_gen_ptrs, which is then used to set s.len with a larger than allocated length for the variable array. Fix it...

Open CVE record
ProductLinux Linux, linux kernel, debian linux
Affected versions>= 073862ba5d249c20bd5c49fc6d904ff0e1f6a672 < 3cdc34d76c4f777579e28ad373979d36c030cfd3, >= 073862ba5d249c20bd5c49fc6d904ff0e1f6a672 < 7b0e64583eab8c1d896b47e5dd0bf2e7d86ec41f, >= 073862ba5d249c20bd5c49fc6d904ff0e1f6a672 < 0c3248bc708a7797be573214065cf908ff1f54c7, >= 073862ba5d249c20bd5c49fc6d904ff0e1f6a672 < 9518b79bfd2fbf99fa9b7e8e36bcb1825e7ba030, >= 073862ba5d249c20bd5c49fc6d904ff0e1f6a672 < 2d60ff5874aefd006717ca5e22ac1e25eac29c42, >= 073862ba5d249c20bd5c49fc6d904ff0e1f6a672 < b6dbfd5bcc267a95a0bf1bf96af46243f96ec6cd, >= 073862ba5d249c20bd5c49fc6d904ff0e1f6a672 < f4f94587e1bf87cb40ec33955a9d90148dd026ab, >= 073862ba5d249c20bd5c49fc6d904ff0e1f6a672 < a26ff37e624d12e28077e5b24d2b264f62764ad6, >= 561331eae0a03d0c4cf60f3cf485aa3e8aa5ab48, >= a2c82f7bee1ffa9eafa1fb0bd886a7eea8c9e497, >= 3.0.19 < 3.1, >= 3.2.3 < 3.3, >= 3.3, >= 3.3.1 < 4.19.314, >= 4.20 < 5.4.276, >= 5.5 < 5.10.217, >= 5.11 < 5.15.159, >= 5.16 < 6.1.91, >= 6.2 < 6.6.31, >= 6.7 < 6.8.10
Fixed versions3.1, 3.3, 4.19.314, 5.4.276, 5.10.217, 5.15.159, 6.1.91, 6.6.31, 6.8.10
Priority basisReview · CVSS 7.1 · EPSS 0.31%
01

Identify the affected asset

Confirm whether Linux Linux, linux kernel, debian linux 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: >= 073862ba5d249c20bd5c49fc6d904ff0e1f6a672 < 3cdc34d76c4f777579e28ad373979d36c030cfd3, >= 073862ba5d249c20bd5c49fc6d904ff0e1f6a672 < 7b0e64583eab8c1d896b47e5dd0bf2e7d86ec41f, >= 073862ba5d249c20bd5c49fc6d904ff0e1f6a672 < 0c3248bc708a7797be573214065cf908ff1f54c7, >= 073862ba5d249c20bd5c49fc6d904ff0e1f6a672 < 9518b79bfd2fbf99fa9b7e8e36bcb1825e7ba030, >= 073862ba5d249c20bd5c49fc6d904ff0e1f6a672 < 2d60ff5874aefd006717ca5e22ac1e25eac29c42, >= 073862ba5d249c20bd5c49fc6d904ff0e1f6a672 < b6dbfd5bcc267a95a0bf1bf96af46243f96ec6cd, >= 073862ba5d249c20bd5c49fc6d904ff0e1f6a672 < f4f94587e1bf87cb40ec33955a9d90148dd026ab, >= 073862ba5d249c20bd5c49fc6d904ff0e1f6a672 < a26ff37e624d12e28077e5b24d2b264f62764ad6, >= 561331eae0a03d0c4cf60f3cf485aa3e8aa5ab48, >= a2c82f7bee1ffa9eafa1fb0bd886a7eea8c9e497, >= 3.0.19 < 3.1, >= 3.2.3 < 3.3, >= 3.3, >= 3.3.1 < 4.19.314, >= 4.20 < 5.4.276, >= 5.5 < 5.10.217, >= 5.11 < 5.15.159, >= 5.16 < 6.1.91, >= 6.2 < 6.6.31, >= 6.7 < 6.8.10. 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: 3.1, 3.3, 4.19.314, 5.4.276, 5.10.217, 5.15.159, 6.1.91, 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.