CVE REMEDIATION GUIDE
Review reviewHighFixed-version data available

CVE-2021-23133 remediation guide

Linux Kernel Linux Kernel, linux kernel, fedora

A race condition in Linux kernel SCTP sockets (net/sctp/socket.c) before 5.12-rc8 can lead to kernel privilege escalation from the context of a network service or an unprivileged process. If sctp_destroy_sock is called without sock_net(sk)->sctp.addr_wq_lock then an element is removed from the auto_asconf_splist list without any proper locking. This can be exploited by an attacker with network service privileges to escalate to root or from the context of an unprivileged user directly if a BPF_CGROUP_INET_SOCK_CREATE is attached which denies creation of some SCTP socket.

Open CVE record
ProductLinux Kernel Linux Kernel, linux kernel, fedora
Affected versions>= unspecified < 5.12-rc8, < 4.4.269, >= 4.5 < 4.9.269, >= 4.10 < 4.14.233, >= 4.15 < 4.19.191, >= 4.20 < 5.4.119, >= 5.5 < 5.10.37, >= 5.11 < 5.11.21, >= 5.12 < 5.12.4, 32, 33, 34, 9.0
Fixed versions4.4.269, 4.9.269, 4.14.233, 4.19.191, 5.4.119, 5.10.37, 5.11.21, 5.12.4
Priority basisReview · CVSS 7 · EPSS 0.47%
01

Identify the affected asset

Confirm whether Linux Kernel Linux Kernel, linux kernel, fedora 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: >= unspecified < 5.12-rc8, < 4.4.269, >= 4.5 < 4.9.269, >= 4.10 < 4.14.233, >= 4.15 < 4.19.191, >= 4.20 < 5.4.119, >= 5.5 < 5.10.37, >= 5.11 < 5.11.21, >= 5.12 < 5.12.4, 32, 33, 34, 9.0. 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.4.269, 4.9.269, 4.14.233, 4.19.191, 5.4.119, 5.10.37, 5.11.21, 5.12.4. 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.