SECUFOCUSNOW
Home›CVE index›CVE-2022-48892
Review reviewHigh

CVE-2022-48892

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: sched/core: Fix use-after-free bug in dup_user_cpus_ptr() Since commit 07ec77a1d4e8 ("sched: Allow task CPU affinity to be restricted on asymmetric systems"), the setting and clearing of user_cpus_ptr are done under pi_lock for arm64 architecture. However, dup_user_cpus_ptr() accesses user_cpus_ptr without any lock protection. Since sched_setaffinity() can be invoked from another process, the process being modified may be undergoing fork() at the same time. When racing with the clearing of user_cpus_ptr in __set_cpus_allowe...

CVSS
7.8
EPSS
-
- percentile
CISA KEV
Not listed
Published
2024.08.21
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability-
Technical severityCVSS 7.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: sched/core: Fix use-after-free bug in dup_user_cpus_ptr() Since commit 07ec77a1d4e8 ("sched: Allow task CPU affinity to be restricted on asymmetric systems"), the setting and clearing of user_cpus_ptr are done under pi_lock for arm64 architecture. However, dup_user_cpus_ptr() accesses user_cpus_ptr without any lock protection. Since sched_setaffinity() can be invoked from another process, the process being modified may be undergoing fork() at the same time. When racing with the clearing of user_cpus_ptr in __set_cpus_allowe...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 07ec77a1d4e82526e1588979fff2f024f8e96df2 < b22faa21b6230d5eccd233e1b7e0026a5002b287, >= 07ec77a1d4e82526e1588979fff2f024f8e96df2 < 7b5cc7fd1789ea5dbb942c9f8207b076d365badc, >= 07ec77a1d4e82526e1588979fff2f024f8e96df2 < 87ca4f9efbd7cc649ff43b87970888f2812945b8, >= 5.15, >= 5.15 < 5.15.89, >= 5.16 < 6.1.7
Fixed versions
5.15.89, 6.1.7

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-415, CWE-416