CVE-2022-49744

Source
https://nvd.nist.gov/vuln/detail/CVE-2022-49744
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-49744.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2022-49744
Related
Published
2025-03-27T17:15:39Z
Modified
2025-03-28T18:11:49Z
Summary
[none]
Details

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(), dstvma is not guaranteed to have VMUFFD_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 dstvma with srcvma the warning & comment it all makes sense too.

Hugetlb did exactly the right here (copyhugetlbpage_range()). Fix the general path.

Reproducer:

https://github.com/xupengfe/syzkallerlogs/blob/main/221208115556copypage_range/repro.c

Bugzilla report: https://bugzilla.kernel.org/show_bug.cgi?id=216808

References

Affected packages

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
6.1.11-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
6.1.11-1

Ecosystem specific

{
    "urgency": "not yet assigned"
}