Review reviewHigh

CVE-2024-27022

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: fork: defer linking file vma until vma is fully initialized Thorvald reported a WARNING [1]. And the root cause is below race: CPU 1 CPU 2 fork hugetlbfs_fallocate dup_mmap hugetlbfs_punch_hole i_mmap_lock_write(mapping); vma_interval_tree_insert_after -- Child vma is visible through i_mmap tree. i_mmap_unlock_write(mapping); hugetlb_dup_vma_private -- Clear vma_lock outside i_mmap_rwsem! i_mmap_lock_write(mapping); hugetlb_vmdelete_list vma_interval_tree_foreach hugetlb_vma_trylock_write -- Vma_lock is cleared. tmp->vm_ops...

CVSS
7.8
EPSS
0.27%
19.0% percentile
CISA KEV
Not listed
Published
2024.05.01
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.27%
Technical severityCVSS 7.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: fork: defer linking file vma until vma is fully initialized Thorvald reported a WARNING [1]. And the root cause is below race: CPU 1 CPU 2 fork hugetlbfs_fallocate dup_mmap hugetlbfs_punch_hole i_mmap_lock_write(mapping); vma_interval_tree_insert_after -- Child vma is visible through i_mmap tree. i_mmap_unlock_write(mapping); hugetlb_dup_vma_private -- Clear vma_lock outside i_mmap_rwsem! i_mmap_lock_write(mapping); hugetlb_vmdelete_list vma_interval_tree_foreach hugetlb_vma_trylock_write -- Vma_lock is cleared. tmp->vm_ops...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 8d9bfb2608145cf3e408428c224099e1585471af < 2e5cbab8ccbfc7d4a3d8a21d3c2a1f2c1aa29b5b, >= 8d9bfb2608145cf3e408428c224099e1585471af < abdb88dd272bbeb93efe01d8e0b7b17e24af3a34, >= 8d9bfb2608145cf3e408428c224099e1585471af < 35e351780fa9d8240dd6f7e4f245f9ea37e96c19, >= 6.1, >= 6.1 < 6.1.90, >= 6.2 < 6.6.30, >= 6.7 < 6.8.8, 6.9
Fixed versions
6.1.90, 6.6.30, 6.8.8

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-908
CVE-2024-27022 — Linux Linux, linux kernel | SECUFOCUS NOW