Review reviewHigh

CVE-2022-48988

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: memcg: fix possible use-after-free in memcg_write_event_control() memcg_write_event_control() accesses the dentry->d_name of the specified control fd to route the write call. As a cgroup interface file can't be renamed, it's safe to access d_name as long as the specified file is a regular cgroup file. Also, as these cgroup interface files can't be removed before the directory, it's safe to access the parent too. Prior to 347c4a874710 ("memcg: remove cgroup_event->cft"), there was a call to __file_cft() which verified that t...

CVSS
7
EPSS
0.24%
15.7% percentile
CISA KEV
Not listed
Published
2024.10.22
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

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

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: memcg: fix possible use-after-free in memcg_write_event_control() memcg_write_event_control() accesses the dentry->d_name of the specified control fd to route the write call. As a cgroup interface file can't be renamed, it's safe to access d_name as long as the specified file is a regular cgroup file. Also, as these cgroup interface files can't be removed before the directory, it's safe to access the parent too. Prior to 347c4a874710 ("memcg: remove cgroup_event->cft"), there was a call to __file_cft() which verified that t...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 347c4a8747104a945ecced358944e42879176ca5 < b77600e26fd48727a95ffd50ba1e937efb548125, >= 347c4a8747104a945ecced358944e42879176ca5 < e1ae97624ecf400ea56c238bff23e5cd139df0b8, >= 347c4a8747104a945ecced358944e42879176ca5 < 35963b31821920908e397146502066f6b032c917, >= 347c4a8747104a945ecced358944e42879176ca5 < f1f7f36cf682fa59db15e2089039a2eeb58ff2ad, >= 347c4a8747104a945ecced358944e42879176ca5 < aad8bbd17a1d586005feb9226c2e9cfce1432e13, >= 347c4a8747104a945ecced358944e42879176ca5 < 0ed074317b835caa6c03bcfa8f133365324673dc, >= 347c4a8747104a945ecced358944e42879176ca5 < 4a7ba45b1a435e7097ca0f79a847d0949d0eb088, >= 3.14, >= 3.14 < 4.14.302, >= 4.15 < 4.19.269, >= 4.20 < 5.4.227, >= 5.5 < 5.10.159, >= 5.11 < 5.15.83, >= 5.16 < 6.0.13, 6.1
Fixed versions
4.14.302, 4.19.269, 5.4.227, 5.10.159, 5.15.83, 6.0.13

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