CVE-2023-53484

lib: cpu_rmap: Avoid use after free on rmap->obj array entries

HIGH
7.8
CVSS Score
Published: October 1, 2025 at 11:42 AM UTC
Updated: October 15, 2026 at 10:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

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 code does not suffer from this since there are no cases where irq_set_affinity_notifier(irq, NULL) (note the NULL passed for the notify arg) is called, followed by a call to free_irq_cpu_rmap() so we don't hit and issue. Subsequent patches in this series excersize this flow, hence the required fix.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.8.1 ≤ v < 4.14.3164.15 ≤ v < 4.19.2844.20 ≤ v < 5.4.2445.11 ≤ v < 5.15.1135.16 ≤ v < 6.1.305.5 ≤ v < 5.10.1816.2 ≤ v < 6.3.43.83.8 rc43.8 rc53.8 rc63.8 rc7896f97ea95c1d29c0520ee0766b66b7f64cb967c
Vendor states this is fixed in 4e0473f1060aa49621d40a113afde24818101d37 (fixed)
Vendor states this is fixed in 67bca5f1d644f4e79b694abd8052a177de81c37f (fixed)
Vendor states this is fixed in 981f339d2905b6a92ef59358158b326493aecac5 (fixed)
Vendor states this is fixed in c6ed54dd90698dc0744d669524cc1c122ded8a16 (fixed)
Vendor states this is fixed in c9115f49cf260d24d8b5f2d9a4b63cb31a627bb4 (fixed)
Vendor states this is fixed in cc2d2b3dbfb0ba57bc027fb7e1121250c50e4000 (fixed)
Vendor states this is fixed in d1308bd0b24cb1d78fa2747d5fa3e055cc628a48 (fixed)
Vendor states this is fixed in f748e15253833b771acbede14ea98f50831ac289 (fixed)
Vendor states this is fixed in 3.8 (unaffected)
Vendor states this is fixed in 4.14.316 (unaffected)
Vendor states this is fixed in 4.19.284 (unaffected)
Vendor states this is fixed in 5.10.181 (unaffected)
Vendor states this is fixed in 5.15.113 (unaffected)
Vendor states this is fixed in 5.4.244 (unaffected)
Vendor states this is fixed in 6.1.30 (unaffected)
Vendor states this is fixed in 6.3.4 (unaffected)
Vendor states this is fixed in 6.4 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-416

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card