SECUFOCUSNOW
Home›CVE index›CVE-2024-39486
Review reviewHigh

CVE-2024-39486

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: drm/drm_file: Fix pid refcounting race <maarten.lankhorst@linux.intel.com>, Maxime Ripard <mripard@kernel.org>, Thomas Zimmermann <tzimmermann@suse.de> filp->pid is supposed to be a refcounted pointer; however, before this patch, drm_file_update_pid() only increments the refcount of a struct pid after storing a pointer to it in filp->pid and dropping the dev->filelist_mutex, making the following race possible: process A process B ========= ========= begin drm_file_update_pid mutex_lock(&dev->filelist_mutex) rcu_replace_poin...

CVSS
7
EPSS
0.23%
13.8% percentile
CISA KEV
Not listed
Published
2024.07.06
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.23%
Technical severityCVSS 7

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: drm/drm_file: Fix pid refcounting race <maarten.lankhorst@linux.intel.com>, Maxime Ripard <mripard@kernel.org>, Thomas Zimmermann <tzimmermann@suse.de> filp->pid is supposed to be a refcounted pointer; however, before this patch, drm_file_update_pid() only increments the refcount of a struct pid after storing a pointer to it in filp->pid and dropping the dev->filelist_mutex, making the following race possible: process A process B ========= ========= begin drm_file_update_pid mutex_lock(&dev->filelist_mutex) rcu_replace_poin...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 031ddd28008971cce0b5626379b910d0a05fb4dd < 16682588ead4a593cf1aebb33b36df4d1e9e4ffa, >= 1c7a387ffef894b1ab3942f0482dac7a6e0a909c < 0acce2a5c619ef1abdee783d7fea5eac78ce4844, >= 1c7a387ffef894b1ab3942f0482dac7a6e0a909c < 4f2a129b33a2054e62273edd5a051c34c08d96e9, >= 6.6.9 < 6.6.37, >= 6.7, >= 6.7 < 6.9.8, 6.10
Fixed versions
6.6.37, 6.9.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:H/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-416
CVE-2024-39486 — Linux Linux, linux kernel | SECUFOCUS NOW