CVE-2022-49220

See a problem?
Please try reporting it to the source first.
Source
https://nvd.nist.gov/vuln/detail/CVE-2022-49220
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-49220.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2022-49220
Related
Published
2025-02-26T07:00:59Z
Modified
2025-02-26T19:01:05.929050Z
Downstream
Summary
[none]
Details

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 ndpmem && modprobe -r ndpmem

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

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

References

Affected packages

Debian:11 / linux

Package

Name
linux
Purl
pkg:deb/debian/linux?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
5.10.113-1

Affected versions

5.*

5.10.46-4
5.10.46-5
5.10.70-1~bpo10+1
5.10.70-1
5.10.84-1
5.10.92-1~bpo10+1
5.10.92-1
5.10.92-2
5.10.103-1~bpo10+1
5.10.103-1
5.10.106-1

Ecosystem specific 

{
    "urgency": "not yet assigned"
}

Debian:12 / linux

Package

Name
linux
Purl
pkg:deb/debian/linux?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
5.17.3-1

Ecosystem specific 

{
    "urgency": "not yet assigned"
}

Debian:13 / linux

Package

Name
linux
Purl
pkg:deb/debian/linux?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
5.17.3-1

Ecosystem specific 

{
    "urgency": "not yet assigned"
}