Skip to content
TrackCVE
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2022-49220

dax: make sure inodes are flushed before destroy cache

Medium5.5EPSS 0.27%
Published
Updated
Reserved
Assigned by
Linux

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 21 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2022-49220, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.27% · top 81% of all CVEs (7 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 7b6be8444e0f0dd675b54d059793423d3c9b4c03 – < 770d42fff12d8595adda9025a0b92091f543e775
    • affected 7b6be8444e0f0dd675b54d059793423d3c9b4c03 – < ec376f5c11c88c0215d173599db8449cd4196759
    • affected 7b6be8444e0f0dd675b54d059793423d3c9b4c03 – < e2951eaa9398415ac054b7bd80b8163b6838ead4
    • affected 7b6be8444e0f0dd675b54d059793423d3c9b4c03 – < f2a1e0eb70c2d954176c07d75d28742bde30e9f3
    • affected 7b6be8444e0f0dd675b54d059793423d3c9b4c03 – < b786abe7c67c6ef71410c8e23292b3091d616ad1
    • affected 7b6be8444e0f0dd675b54d059793423d3c9b4c03 – < a7e8de822e0b1979f08767c751f6c8a9c1d4ad86
  • Linux · Linux

    • affected 4.12
    • unaffected < 4.12
    • unaffected 5.4.189 – ≤ 5.4.*
    • unaffected 5.10.110 – ≤ 5.10.*
    • unaffected 5.15.33 – ≤ 5.15.*
    • unaffected 5.16.19 – ≤ 5.16.*
    • unaffected 5.17.2 – ≤ 5.17.*
    • unaffected 5.18 – ≤ *

References (6)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-49220 badge
[![CVE-2022-49220](https://trackcve.app/badge/CVE-2022-49220.svg)](https://trackcve.app/cve/CVE-2022-49220)

Record last updated .