| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <2025022656-CVE-2022-49077-6e0c@gregkh> Date: Wed, 26 Feb 2025 02:54:42 +0100 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org> Subject: CVE-2022-49077: mmmremap.c: avoid pointless invalidate_range_start/end on mremap(old_size=0) Description =========== 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. The Linux kernel CVE team has assigned CVE-2022-49077 to this issue. Affected and fixed versions =========================== Fixed in 4.9.311 with commit a05540f3903bd8295e8c4cd90dd3d416239a115b Fixed in 4.14.276 with commit eeaf28e2a0128147d687237e59d5407ee1b14693 Fixed in 4.19.238 with commit e2c328c2a8f9de8b761bd4025b66c63120c55761 Fixed in 5.4.189 with commit c19d8de4e682ec4b0ea2b04a832cd8cc0be3bb31 Fixed in 5.10.111 with commit 7d659cb1763ff17d1c6ee082fa6feb4267c7a30b Fixed in 5.15.34 with commit a04cb99c5d4668fe3f5c0e5b6da1cecd34c3f219 Fixed in 5.16.20 with commit 2358aa84ef6dafcf544a557caaa6b91afb4a0bd2 Fixed in 5.17.3 with commit 04bc13dae4a27b8d030843c85ae452bb2f1d9c1f Fixed in 5.18 with commit 01e67e04c28170c47700c2c226d732bbfedb1ad0 Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2022-49077 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: mm/mremap.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/a05540f3903bd8295e8c4cd90dd3d416239a115b https://git.kernel.org/stable/c/eeaf28e2a0128147d687237e59d5407ee1b14693 https://git.kernel.org/stable/c/e2c328c2a8f9de8b761bd4025b66c63120c55761 https://git.kernel.org/stable/c/c19d8de4e682ec4b0ea2b04a832cd8cc0be3bb31 https://git.kernel.org/stable/c/7d659cb1763ff17d1c6ee082fa6feb4267c7a30b https://git.kernel.org/stable/c/a04cb99c5d4668fe3f5c0e5b6da1cecd34c3f219 https://git.kernel.org/stable/c/2358aa84ef6dafcf544a557caaa6b91afb4a0bd2 https://git.kernel.org/stable/c/04bc13dae4a27b8d030843c85ae452bb2f1d9c1f https://git.kernel.org/stable/c/01e67e04c28170c47700c2c226d732bbfedb1ad0
Powered by blists - more mailing lists