Review reviewHigh

CVE-2023-53484

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: lib: cpu_rmap: Avoid use after free on rmap->obj array entries When calling irq_set_affinity_notifier() with NULL at the notify argument, it will cause freeing of the glue pointer in the corresponding array entry but will leave the pointer in the array. A subsequent call to free_irq_cpu_rmap() will try to free this entry again leading to possible use after free. Fix that by setting NULL to the array entry and checking that we have non-zero at the array entry when iterating over the array in free_irq_cpu_rmap(). The current...

CVSS
7.8
EPSS
0.15%
4.61% percentile
CISA KEV
Not listed
Published
2025.10.01
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

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

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: lib: cpu_rmap: Avoid use after free on rmap->obj array entries When calling irq_set_affinity_notifier() with NULL at the notify argument, it will cause freeing of the glue pointer in the corresponding array entry but will leave the pointer in the array. A subsequent call to free_irq_cpu_rmap() will try to free this entry again leading to possible use after free. Fix that by setting NULL to the array entry and checking that we have non-zero at the array entry when iterating over the array in free_irq_cpu_rmap(). The current...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 896f97ea95c1d29c0520ee0766b66b7f64cb967c < 981f339d2905b6a92ef59358158b326493aecac5, >= 896f97ea95c1d29c0520ee0766b66b7f64cb967c < d1308bd0b24cb1d78fa2747d5fa3e055cc628a48, >= 896f97ea95c1d29c0520ee0766b66b7f64cb967c < cc2d2b3dbfb0ba57bc027fb7e1121250c50e4000, >= 896f97ea95c1d29c0520ee0766b66b7f64cb967c < f748e15253833b771acbede14ea98f50831ac289, >= 896f97ea95c1d29c0520ee0766b66b7f64cb967c < c6ed54dd90698dc0744d669524cc1c122ded8a16, >= 896f97ea95c1d29c0520ee0766b66b7f64cb967c < c9115f49cf260d24d8b5f2d9a4b63cb31a627bb4, >= 896f97ea95c1d29c0520ee0766b66b7f64cb967c < 67bca5f1d644f4e79b694abd8052a177de81c37f, >= 896f97ea95c1d29c0520ee0766b66b7f64cb967c < 4e0473f1060aa49621d40a113afde24818101d37, >= 3.8, >= 3.8.1 < 4.14.316, >= 4.15 < 4.19.284, >= 4.20 < 5.4.244, >= 5.5 < 5.10.181, >= 5.11 < 5.15.113, >= 5.16 < 6.1.30, >= 6.2 < 6.3.4, 3.8
Fixed versions
4.14.316, 4.19.284, 5.4.244, 5.10.181, 5.15.113, 6.1.30, 6.3.4

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-416