Answer in brief
CVE-2023-53484 records a High severity (CVSS 7.8) vulnerability in lib: cpu_rmap: Avoid use after free on rmap->obj array entries. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2023-53484 records a High severity (CVSS 7.8) vulnerability in lib: cpu_rmap: Avoid use after free on rmap->obj array entries. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:3.8:-:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:3.8:rc4:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:3.8:rc5:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:3.8:rc6:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:3.8:rc7:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=896f97ea95c1d29c0520ee0766b66b7f64cb967c <981f339d2905b6a92ef59358158b326493aecac5 || >=896f97ea95c1d29c0520ee0766b66b7f64cb967c <d1308bd0b24cb1d78fa2747d5fa3e055cc628a48 || >=896f97ea95c1d29c0520ee0766b66b7f64cb967c <cc2d2b3dbfb0ba57bc027fb7e1121250c50e4000 || >=896f97ea95c1d29c0520ee0766b66b7f64cb967c <f748e15253833b771acbede14ea98f50831ac289 || >=896f97ea95c1d29c0520ee0766b66b7f64cb967c <c6ed54dd90698dc0744d669524cc1c122ded8a16 || >=896f97ea95c1d29c0520ee0766b66b7f64cb967c <c9115f49cf260d24d8b5f2d9a4b63cb31a627bb4 || >=896f97ea95c1d29c0520ee0766b66b7f64cb967c <67bca5f1d644f4e79b694abd8052a177de81c37f || >=896f97ea95c1d29c0520ee0766b66b7f64cb967c <4e0473f1060aa49621d40a113afde24818101d37 | 981f339d2905b6a92ef59358158b326493aecac5, d1308bd0b24cb1d78fa2747d5fa3e055cc628a48, cc2d2b3dbfb0ba57bc027fb7e1121250c50e4000, f748e15253833b771acbede14ea98f50831ac289, c6ed54dd90698dc0744d669524cc1c122ded8a16, c9115f49cf260d24d8b5f2d9a4b63cb31a627bb4, 67bca5f1d644f4e79b694abd8052a177de81c37f, 4e0473f1060aa49621d40a113afde24818101d37 |
| Linux/Linuxgeneric | 3.8 | Not reported |
Published upstream
Oct 1, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:3.8:-:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:3.8:rc4:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:3.8:rc5:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:3.8:rc6:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:3.8:rc7:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=896f97ea95c1d29c0520ee0766b66b7f64cb967c <981f339d2905b6a92ef59358158b326493aecac5 || >=896f97ea95c1d29c0520ee0766b66b7f64cb967c <d1308bd0b24cb1d78fa2747d5fa3e055cc628a48 || >=896f97ea95c1d29c0520ee0766b66b7f64cb967c <cc2d2b3dbfb0ba57bc027fb7e1121250c50e4000 || >=896f97ea95c1d29c0520ee0766b66b7f64cb967c <f748e15253833b771acbede14ea98f50831ac289 || >=896f97ea95c1d29c0520ee0766b66b7f64cb967c <c6ed54dd90698dc0744d669524cc1c122ded8a16 || >=896f97ea95c1d29c0520ee0766b66b7f64cb967c <c9115f49cf260d24d8b5f2d9a4b63cb31a627bb4 || >=896f97ea95c1d29c0520ee0766b66b7f64cb967c <67bca5f1d644f4e79b694abd8052a177de81c37f || >=896f97ea95c1d29c0520ee0766b66b7f64cb967c <4e0473f1060aa49621d40a113afde24818101d37 | 981f339d2905b6a92ef59358158b326493aecac5, d1308bd0b24cb1d78fa2747d5fa3e055cc628a48, cc2d2b3dbfb0ba57bc027fb7e1121250c50e4000, f748e15253833b771acbede14ea98f50831ac289, c6ed54dd90698dc0744d669524cc1c122ded8a16, c9115f49cf260d24d8b5f2d9a4b63cb31a627bb4, 67bca5f1d644f4e79b694abd8052a177de81c37f, 4e0473f1060aa49621d40a113afde24818101d37 |
| Linux/Linuxgeneric | 3.8 | Not reported |
Published upstream
Oct 1, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.