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
Conclusion & alert: CVE-2022-49744 is rated Low Risk (26.4/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.04%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.
Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.
EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).
| # | Date | Old EPSS score | New EPSS score | Delta (New - Old) |
|---|---|---|---|---|
| 1 | 2026-05-07 | 0.07% | 0.04% | -0.03% |
| 2 | 2026-01-21 | 0.02% | 0.07% | +0.06% |
| 3 | 2025-03-28 | — | 0.02% | — |
Full EPSS history (3 records total)
CVSS metrics for this CVE.
| Base score | Version | Severity | Vector | Exploitability | Impact | Score source |
|---|---|---|---|---|---|---|
| 5.5 | 3.1 | MEDIUM |
|
1.8 | 3.6 | [email protected] |
| vendor | priority | summary | link |
|---|---|---|---|
debian
|
unimportant | CVE-2022-49744 unimportant priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. | https://security-tracker.debian.org/tracker/CVE-2022-49744 |
redhat
|
low | — | https://access.redhat.com/security/cve/CVE-2022-49744 |
suse
|
medium | CVE-2022-49744 severity moderate: SUSE including 55 source package names (bpftool-7.3.0-427.13.1.el9_4, cluster-md-kmp-default, …), 268 product×package rows across 45 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Liberty Linux 9, … (45 product lines)): Known Not Affected 239, Fixed 29. | https://www.suse.com/security/cve/CVE-2022-49744/ |
ubuntu
|
medium | CVE-2022-49744 medium priority: Ubuntu including 130 source packages (linux, linux-allwinner-5.19, …), 1040 status rows across 8 suites (bionic, focal, jammy, noble, oracular, trusty, upstream, xenial): DNE 713, ignored 146, not-affected 117, released 64. | https://ubuntu.com/security/CVE-2022-49744 |
| Vendor | Product | Version | Raw CPE |
|---|---|---|---|
| linux | linux_kernel | >= 5.19, < 6.1.11 | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* |
| linux | linux_kernel | 6.2 | cpe:2.3:o:linux:linux_kernel:6.2:rc1:*:*:*:*:*:* |
| linux | linux_kernel | 6.2 | cpe:2.3:o:linux:linux_kernel:6.2:rc2:*:*:*:*:*:* |
| linux | linux_kernel | 6.2 | cpe:2.3:o:linux:linux_kernel:6.2:rc3:*:*:*:*:*:* |
| linux | linux_kernel | 6.2 | cpe:2.3:o:linux:linux_kernel:6.2:rc4:*:*:*:*:*:* |
| linux | linux_kernel | 6.2 | cpe:2.3:o:linux:linux_kernel:6.2:rc5:*:*:*:*:*:* |
| linux | linux_kernel | 6.2 | cpe:2.3:o:linux:linux_kernel:6.2:rc6:*:*:*:*:*:* |