CVE-2022-49744
Last modified
CVE-2022-49744 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: mm/uffd: fix pte marker when fork() without fork event Patch series "mm: Fixes on pte markers". Patch 1 resolves the syzkiller report from Pengfei. Patch 2 further harden pte markers when used with the recent swapin error markers. The major case is we should persist a swapin error marker after fork(), so child shouldn't read a corrupted page. This patch (of 2): When fork(), dst_vma is not guaranteed to have VM_UFFD_WP even if src may have it and has pte marker installed. EPSS estimates a 0.15% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: mm/uffd: fix pte marker when fork() without fork event Patch series "mm: Fixes on pte markers". Patch 1 resolves the syzkiller report from Pengfei. Patch 2 further harden pte markers when used with the recent swapin error markers. The major case is we should persist a swapin error marker after fork(), so child shouldn't read a corrupted page. This patch (of 2): When fork(), dst_vma is not guaranteed to have VM_UFFD_WP even if src may have it and has pte marker installed. The warning is improper along with the comment. The right thing is to inherit the pte marker when needed, or keep the dst pte empty. A vague guess is this happened by an accident when there's the prior patch to introduce src/dst vma into this helper during the uffd-wp feature got developed and I probably messed up in the rebase, since if we replace dst_vma with src_vma the warning & comment it all makes sense too. Hugetlb did exactly the right here (copy_hugetlb_page_range()). Fix the general path. Reproducer: https://github.com/xupengfe/syzkaller_logs/blob/main/221208_115556_copy_page_range/repro.c Bugzilla report: https://bugzilla.kernel.org/show_bug.cgi?id=216808
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 5.19, < 6.1.11 | — |
| Linux | Linux Kernel | 6.2 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2022-49744?
How severe is CVE-2022-49744?
How do I fix CVE-2022-49744?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2022
- CVE-2022-49739In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-4974The Freemius SDK, as used by hundreds of WordPress plugin an…6.3
- CVE-2022-49740In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2022-49741In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49742In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49743In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49745In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49746In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49747In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49748In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49749In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-4975A flaw was found in the Red Hat Advanced Cluster Security (R…8.9
Are you affected by CVE-2022-49744?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
