Skip to content
Fencer Vulns
medium 5.5

CVE-2022-48933 json

netfilter: nf_tables: fix memory leak during stateful obj update

published 2024-08-22 2 y ago modified 2026-06-17 4 mo ago also EUVD-2022-53812

cvss
5.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 11%
public exploits
0
none known

Summary

In the Linux kernel, the following vulnerability has been resolved:

netfilter: nf_tables: fix memory leak during stateful obj update

stateful objects can be updated from the control plane. The transaction logic allocates a temporary object for this purpose.

The ->init function was called for this object, so plain kfree() leaks resources. We must call ->destroy function of the object.

nft_obj_destroy does this, but it also decrements the module refcount, but the update path doesn't increment it.

To avoid special-casing the update object release, do module_get for the update case too and release it via nft_obj_destroy().

Patch / fix

  • Linux Linux 5.4.182, 5.10.103, 5.15.26, 5.16.12, 5.17
  • linux Debian 14, Debian 13, Debian 12 5.16.12-1

debian advisories DEBIAN-CVE-2022-48933

  • linux Ubuntu 20.04 LTS 5.4.0-117.132
  • linux-aws Ubuntu 20.04 LTS 5.4.0-1078.84
  • linux-gcp Ubuntu 20.04 LTS 5.4.0-1078.84
  • linux-ibm Ubuntu 20.04 LTS 5.4.0-1026.29
  • linux-iot Ubuntu 20.04 LTS 5.4.0-1004.6
  • linux-kvm Ubuntu 20.04 LTS 5.4.0-1068.72
  • linux-azure Ubuntu 20.04 LTS 5.4.0-1083.87
  • linux-gkeop Ubuntu 20.04 LTS 5.4.0-1046.48

ubuntu advisories UBUNTU-CVE-2022-48933

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • kernel-rt SLE Micro 5.5 5.14.21-150500.13.94.1
  • kernel-source-rt SLE Micro 5.5 5.14.21-150500.13.94.1
  • kernel-64kb SLES 15 SP5-LTSS, SLE High Performance Computing 15 SP5-LTSS, SLE High Performance Computing 15 SP5-ESPOS 5.14.21-150500.55.103.1
  • kernel-syms SLES for SAP 15 SP5, SLES 15 SP5-LTSS, SLE High Performance Computing 15 SP5-LTSS +1 more 5.14.21-150500.55.103.1
  • kernel-source SLES for SAP 15 SP5, SLES 15 SP5-LTSS, SLE Micro 5.5 +2 more 5.14.21-150500.55.103.1
  • kernel-default SLES for SAP 15 SP5, SLES 15 SP5-LTSS, SLE Micro 5.5 +3 more 5.14.21-150500.55.103.1
  • kernel-obs-build SLES for SAP 15 SP5, SLES 15 SP5-LTSS, SLE High Performance Computing 15 SP5-LTSS +1 more 5.14.21-150500.55.103.1
  • kernel-default-base SLES for SAP 15 SP5, SLES 15 SP5-LTSS, SLE Micro 5.5 +2 more 5.14.21-150500.55.103.1.150500.6.49.1

suse advisories SUSE-SU-2025:01640-1SUSE-SU-2025:01620-1SUSE-SU-2024:3249-1SUSE-SU-2024:3225-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-48933 updated cvss 6.1

kernel: netfilter: nf_tables: fix memory leak during stateful obj update

  • Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more
    affected: no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.21% chance of exploitation in the next 30 days, higher than 11% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected products

  • Linux Linux

Classification

Weakness
  • CWE-401 Missing Release of Memory after Effective Lifetime
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.