Go to homepageCyberStrike

Menu

Star on GitHub · 3.4k
Sign inDownload

CVE-2022-48986

7.8 · HIGH

In the Linux kernel, the following vulnerability has been resolved: mm/gup: fix gup_pud_range() for dax For dax pud, pud_huge() returns true on x86.

Published Oct 21, 2024EPSS 0.26%

Overview

CVE-2022-48986 is a high-severity vulnerability. It was published on October 21, 2024 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

mm/gup: fix gup_pud_range() for dax

For dax pud, pud_huge() returns true on x86. So the function works as long

as hugetlb is configured. However, dax doesn't depend on hugetlb.

Commit 414fd080d125 ("mm/gup: fix gup_pmd_range() for dax") fixed

devmap-backed huge PMDs, but missed devmap-backed huge PUDs. Fix this as

well.

This fixes the below kernel panic:

general protection fault, probably for non-canonical address 0x69e7c000cc478: 0000 [#1] SMP

< snip >

Call Trace:

<TASK>

get_user_pages_fast+0x1f/0x40

iov_iter_get_pages+0xc6/0x3b0

? mempool_alloc+0x5d/0x170

bio_iov_iter_get_pages+0x82/0x4e0

? bvec_alloc+0x91/0xc0

? bio_alloc_bioset+0x19a/0x2a0

blkdev_direct_IO+0x282/0x480

? __io_complete_rw_common+0xc0/0xc0

? filemap_range_has_page+0x82/0xc0

generic_file_direct_write+0x9d/0x1a0

? inode_update_time+0x24/0x30

__generic_file_write_iter+0xbd/0x1e0

blkdev_write_iter+0xb4/0x150

? io_import_iovec+0x8d/0x340

io_write+0xf9

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/04edfa3dc06ecfc6133a33bc7271298782dee875Refgit.kernel.org/stable/c/3ac29732a2ffa64c7de13a072b0f2848b9c11037Refgit.kernel.org/stable/c/e06d13c36ded750c72521b600293befebb4e56c5Refgit.kernel.org/stable/c/f1cf856123ceb766c49967ec79b841030fa1741fRefgit.kernel.org/stable/c/fcd0ccd836ffad73d98a66f6fea7b16f735ea920

How CyberStrike helps

Frequently asked questions

What is CVE-2022-48986?

CVE-2022-48986 is a high-severity vulnerability. It was published on October 21, 2024 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2022-48986?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2022-48986?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2022-48986?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2022-48986 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2022

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999
LiveWatch live →