Bug 1903249 (CVE-2020-29374) - CVE-2020-29374 kernel: the get_user_pages implementation when used for a copy-on-write page does not properly consider the semantics of read operations and therefore can grant unintended read access
Summary: CVE-2020-29374 kernel: the get_user_pages implementation when used for a copy...
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2020-29374
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1975127 1975128 1975129 1975130 1903251 1974670 1974671 1974672 1974673
Blocks: 1903252
TreeView+ depends on / blocked
 
Reported: 2020-12-01 17:15 UTC by Guilherme de Almeida Suckevicz
Modified: 2021-12-20 23:17 UTC (History)
43 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
An issue was discovered in the Linux kernel related to mm/gup.c and mm/huge_memory.c. The get_user_pages (aka gup) implementation, when used for a copy-on-write page, does not properly consider the semantics of read operations and therefore can grant unintended read access.
Clone Of:
Environment:
Last Closed: 2021-12-15 11:21:01 UTC
Embargoed:

Attachments (Terms of Use)

Description Guilherme de Almeida Suckevicz 2020-12-01 17:15:38 UTC 
An issue was discovered in the Linux kernel before 5.7.3, related to mm/gup.c and mm/huge_memory.c. The get_user_pages (aka gup) implementation, when used for a copy-on-write page, does not properly consider the semantics of read operations and therefore can grant unintended write access.

Reference:
https://bugs.chromium.org/p/project-zero/issues/detail?id=2045

Upstream commit:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=17839856fd588f4ab6b789f482ed3ffd7c403e1f
Comment 1 Guilherme de Almeida Suckevicz 2020-12-01 17:16:34 UTC 
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 1903251]
Comment 2 Justin M. Forbes 2020-12-02 14:17:58 UTC 
This was fixed for Fedora with the 5.6.19 stable kernel updates.
Note You need to log in before you can comment on or make changes to this bug.