CVSS 3.1
5.5 mediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HMedium (5.5) in linux linux kernel. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExplain CVE-2022-49760 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-49760?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-49760?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-49760 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Linux | 5.19 and later |
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 6.1 | 6.1.8 |
| Linux | later releases | 6.2 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13, 14 | linux | 6.1.8-1 | DEBIAN-CVE-2022-49760 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2022-49760 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2022-49760 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2022-49760 |
| Ubuntu | 22.04:LTS | linux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 more | no fix listed | UBUNTU-CVE-2022-49760 |
| Ubuntu | 24.04:LTS | linux-realtime, linux-raspi-realtime | no fix listed | UBUNTU-CVE-2022-49760 |
| Red Hat | enterprise_linux:9::appstream | rv, perf, rtla and 24 more | 0:5.14.0-362.8.1.el9_3 | RHSA-2023:6583 |
| Red Hat | enterprise_linux:9::appstream, enterprise_linux:9::crb, enterprise_linux:9::nfv and 1 more | bpftool-debuginfo | 0:7.2.0-362.8.1.el9_3 | RHSA-2023:6583 |
| Red Hat | enterprise_linux:9::baseos | bpftool, bpftool-debuginfo | 0:7.2.0-362.8.1.el9_3 | RHSA-2023:6583 |
| Red Hat | enterprise_linux:9::baseos | kernel, kernel-64k, kernel-core and 41 more | 0:5.14.0-362.8.1.el9_3 | RHSA-2023:6583 |
| Red Hat | enterprise_linux:9::crb | libperf, perf-debuginfo, kernel-debuginfo and 12 more | 0:5.14.0-362.8.1.el9_3 | RHSA-2023:6583 |
| Red Hat | enterprise_linux:9::nfv | kernel-rt, kernel-rt-kvm, kernel-rt-core and 20 more | 0:5.14.0-362.8.1.el9_3 | RHSA-2023:6583 |
| Red Hat | enterprise_linux:9::realtime | kernel-rt, kernel-rt-core, perf-debuginfo and 18 more | 0:5.14.0-362.8.1.el9_3 | RHSA-2023:6583 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat.
Red Hat rates this Low.
A low severity flaw was found in the Linux kernel's hugetlb memory management. The hugetlb_change_protection() function mishandles userfaultfd write-protect (uffd-wp) PTE markers: write-protecting an existing uffd-wp PTE marker a second time, or unprotecting one, takes the "!huge_pte_none(pte)" path and corrupts the marker. A later operation that encounters the corrupted marker, for example fallocate(FALLOC_FL_PUNCH_HOLE) on a hugetlb-backed memfd file range, then treats the marker as a present PTE mapping a garbage page and triggers a kernel BUG, resulting in a local denial of service (system crash). Exploitation requires local access and the ability to register userfaultfd write-protect mode on hugetlb-backed memory, an uncommon configuration, which is reflected in the Red Hat Low impact rating (CVSS 4.1, availability impact only). The substantially higher CVE.org score of 7.8 (high confidentiality, integrity, and availability impact) is not supported by the technical analysis, which demonstrates only availability impact from a kernel BUG. In Red Hat Enterprise Linux 9 the kernel and kernel-rt packages are affected; the fix is deferred for the affected RHEL 9 streams because the flaw is low severity and requires privileged local access in an uncommon hugetlb plus userfaultfd write-protect configuration to trigger, leaving a residual risk of a local denial of service in such configurations. Red Hat Enterprise Linux 6, 7, 8, and 10, and Red Hat In-Vehicle OS are not affected because the vulnerable code is not present.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | kernel | Not affected | |
| Red Hat Enterprise Linux 6 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 8 | kernel | Not affected | |
| Red Hat Enterprise Linux 8 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 9 | kernel | Fix deferred | |
| Red Hat Enterprise Linux 9 | kernel-rt | Fix deferred |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2022-49760.