CVE-2022-49077 json
mmmremap.c: avoid pointless invalidate_range_start/end on mremap(old_size=0)
published 2025-02-26 20 mo ago modified 2026-11-05 3 d ago also EUVD-2022-55127
- 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 16%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
mmmremap.c: avoid pointless invalidate_range_start/end on mremap(old_size=0)
If an mremap() syscall with old_size=0 ends up in move_page_tables(), it will call invalidate_range_start()/invalidate_range_end() unnecessarily, i.e. with an empty range.
This causes a WARN in KVM's mmu_notifier. In the past, empty ranges have been diagnosed to be off-by-one bugs, hence the WARNing. Given the low (so far) number of unique reports, the benefits of detecting more buggy callers seem to outweigh the cost of having to fix cases such as this one, where userspace is doing something silly. In this particular case, an early return from move_page_tables() is enough to fix the issue.
Patch / fix
- Linux Linux 4.9.311, 4.14.276, 4.19.238, 5.4.189, 5.10.111, 5.15.34, 5.16.20, 5.17.3, 5.18
- linux Debian 14, Debian 13, Debian 12 5.17.3-1
debian advisories DEBIAN-CVE-2022-49077
- linux Ubuntu 18.04 LTS 4.15.0-189.200
- linux Ubuntu 20.04 LTS 5.4.0-117.132
- linux Ubuntu 22.04 LTS 5.15.0-37.39
- linux-aws Ubuntu 18.04 LTS 4.15.0-1137.148
- 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
ubuntu advisories UBUNTU-CVE-2022-49077
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
- git.kernel.org/stable/c/a05540f3903bd8295e8c4cd90dd3d416239a115b commit
- git.kernel.org/stable/c/eeaf28e2a0128147d687237e59d5407ee1b14693 commit
- git.kernel.org/stable/c/e2c328c2a8f9de8b761bd4025b66c63120c55761 commit
- git.kernel.org/stable/c/c19d8de4e682ec4b0ea2b04a832cd8cc0be3bb31 commit
- git.kernel.org/stable/c/7d659cb1763ff17d1c6ee082fa6feb4267c7a30b commit
- git.kernel.org/stable/c/a04cb99c5d4668fe3f5c0e5b6da1cecd34c3f219 commit
- git.kernel.org/stable/c/2358aa84ef6dafcf544a557caaa6b91afb4a0bd2 commit
- git.kernel.org/stable/c/04bc13dae4a27b8d030843c85ae452bb2f1d9c1f commit
- git.kernel.org/stable/c/01e67e04c28170c47700c2c226d732bbfedb1ad0 commit
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-49077 updated cvss 5.5
kernel: mmmremap.c: avoid pointless invalidate_range_start/end on mremap(old_size=0)
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more 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 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 moreaffected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 10 kernelnot 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.25% chance of exploitation in the next 30 days, higher than 16% 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-193 Off-by-one Error
- Technology feeds
References
-
git.kernel.org
/stable/c/a05540f3903bd8295e8c4cd90dd3d416239a115b
patch
-
git.kernel.org
/stable/c/eeaf28e2a0128147d687237e59d5407ee1b14693
patch
-
git.kernel.org
/stable/c/e2c328c2a8f9de8b761bd4025b66c63120c55761
patch
-
git.kernel.org
/stable/c/c19d8de4e682ec4b0ea2b04a832cd8cc0be3bb31
patch
-
git.kernel.org
/stable/c/7d659cb1763ff17d1c6ee082fa6feb4267c7a30b
patch
-
git.kernel.org
/stable/c/a04cb99c5d4668fe3f5c0e5b6da1cecd34c3f219
patch
-
git.kernel.org
/stable/c/2358aa84ef6dafcf544a557caaa6b91afb4a0bd2
patch
-
git.kernel.org
/stable/c/04bc13dae4a27b8d030843c85ae452bb2f1d9c1f
patch
-
git.kernel.org
/stable/c/01e67e04c28170c47700c2c226d732bbfedb1ad0
patch
Sources
- CVE List CVE-2022-49077
- NVD CVE-2022-49077
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.