Skip to content
Fencer Vulns
medium 5.5

CVE-2022-49220 json

dax: make sure inodes are flushed before destroy cache

published 2025-02-26 20 mo ago modified 2026-11-05 3 d ago also EUVD-2022-55006

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

Summary

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

dax: make sure inodes are flushed before destroy cache

A bug can be triggered by following command

$ modprobe nd_pmem && modprobe -r nd_pmem

[ 10.060014] BUG dax_cache (Not tainted): Objects remaining in dax_cache on __kmem_cache_shutdown() [ 10.060938] Slab 0x0000000085b729ac objects=9 used=1 fp=0x000000004f5ae469 flags=0x200000000010200(slab|head|node) [ 10.062433] Call Trace: [ 10.062673] dump_stack_lvl+0x34/0x44 [ 10.062865] slab_err+0x90/0xd0 [ 10.063619] __kmem_cache_shutdown+0x13b/0x2f0 [ 10.063848] kmem_cache_destroy+0x4a/0x110 [ 10.064058] __x64_sys_delete_module+0x265/0x300

This is caused by dax_fs_exit() not flushing inodes before destroy cache. To fix this issue, call rcu_barrier() before destroy cache.

Patch / fix

  • Linux Linux 5.4.189, 5.10.110, 5.15.33, 5.16.19, 5.17.2, 5.18
  • linux Debian 14, Debian 13, Debian 12 5.17.3-1

debian advisories DEBIAN-CVE-2022-49220

  • linux Ubuntu 20.04 LTS 5.4.0-117.132
  • linux Ubuntu 22.04 LTS 5.15.0-37.39
  • linux-aws Ubuntu 20.04 LTS 5.4.0-1078.84
  • linux-aws Ubuntu 22.04 LTS 5.15.0-1011.14
  • linux-gcp Ubuntu 20.04 LTS 5.4.0-1078.84
  • linux-gcp Ubuntu 22.04 LTS 5.15.0-1008.12
  • linux-gke Ubuntu 22.04 LTS 5.15.0-1008.10
  • linux-ibm Ubuntu 20.04 LTS 5.4.0-1026.29

ubuntu advisories UBUNTU-CVE-2022-49220

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 RHEL 9 5.14.0-362.8.1.el9_3
  • rv RHEL 9 5.14.0-362.8.1.el9_3
  • perf RHEL 9 5.14.0-362.8.1.el9_3
  • rtla RHEL 9 5.14.0-362.8.1.el9_3
  • bpftool RHEL 9 7.2.0-362.8.1.el9_3
  • libperf RHEL 9 5.14.0-362.8.1.el9_3
  • kernel-rt RHEL 9 5.14.0-362.8.1.el9_3
  • kernel-64k RHEL 9 5.14.0-362.8.1.el9_3

red hat advisories RHSA-2023:6583

  • kernel-syms SLES LTSS Extended Security 12 SP5, SLES 12 SP5-LTSS 4.12.14-122.255.1
  • kernel-source SLES LTSS Extended Security 12 SP5, SLES 12 SP5-LTSS 4.12.14-122.255.1
  • kernel-default SLES LTSS Extended Security 12 SP5, SLES 12 SP5-LTSS, SLE Live Patching 12 SP5 4.12.14-122.255.1
  • kgraft-patch-SLE12-SP5_Update_67 SLE Live Patching 12 SP5 1-8.5.1

suse advisories SUSE-SU-2025:1293-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-49220 updated cvss 5.5

kernel: dax: make sure inodes are flushed before destroy cache

  • Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more
    affected: no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more
    affected: no fix available
  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 10 kernel
    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
3 d ago

Exploit prediction

0.27% chance of exploitation in the next 30 days, higher than 19% 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

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.