NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 31/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Linux Linux 4e0473f1060aa49621d40a113afde24818101d37, 67bca5f1d644f4e79b694abd8052a177de81c37f, 981f339d2905b6a92ef59358158b326493aecac5.

Low priority for now. Upgrade to Linux Linux 4e0473f1060aa49621d40a113afde24818101d37, 67bca5f1d644f4e79b694abd8052a177de81c37f, 981f339d2905b6a92ef59358158b326493aecac5 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

BDU:2026-03342

Published: Oct 1, 2025
Updated: Oct 15, 2026
EPSS: 0.1% · 5th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 7.8
CNA · Linux: 7.8; agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

linux linux kernel3.8.1 and later · before 4.14.316
linux linux kernel4.15 and later · before 4.19.284
linux linux kernel4.20 and later · before 5.4.244
linux linux kernel5.5 and later · before 5.10.181
linux linux kernel5.11 and later · before 5.15.113
linux linux kernel5.16 and later · before 6.1.30
linux linux kernel6.2 and later · before 6.3.4
linux linux kernel3.8

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

Linux Linux
- 3.8affected
- 896f97ea95c1d29c0520ee0766b66b7f64cb967c and later · before 981f339d2905b6a92ef59358158b326493aecac5affected · git
- 896f97ea95c1d29c0520ee0766b66b7f64cb967c and later · before d1308bd0b24cb1d78fa2747d5fa3e055cc628a48affected · git
- 896f97ea95c1d29c0520ee0766b66b7f64cb967c and later · before cc2d2b3dbfb0ba57bc027fb7e1121250c50e4000affected · git
- 896f97ea95c1d29c0520ee0766b66b7f64cb967c and later · before f748e15253833b771acbede14ea98f50831ac289affected · git
- 896f97ea95c1d29c0520ee0766b66b7f64cb967c and later · before c6ed54dd90698dc0744d669524cc1c122ded8a16affected · git
- 896f97ea95c1d29c0520ee0766b66b7f64cb967c and later · before c9115f49cf260d24d8b5f2d9a4b63cb31a627bb4affected · git
- 896f97ea95c1d29c0520ee0766b66b7f64cb967c and later · before 67bca5f1d644f4e79b694abd8052a177de81c37faffected · git
- 896f97ea95c1d29c0520ee0766b66b7f64cb967c and later · before 4e0473f1060aa49621d40a113afde24818101d37affected · git
- before 3.8not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	linux	before 6.1.37-1	6.1.37-1
Debian:13	linux	before 6.3.7-1	6.3.7-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now

Published before and after this one in the same product

← EarlierCVE-2023-53481Oct 1, 2025 · ubi: ubi_wl_put_peb: Fix infinite loop when wear-leveling work failed
22Monitor
← EarlierCVE-2023-53482Oct 1, 2025 · iommu: Fix error unwind in iommu_group_alloc()
22Monitor
Later →CVE-2023-53487Oct 1, 2025 · powerpc/rtas_flash: allow user copy to flash block cache objects
31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Linux Linux	4e0473f1060aa49621d40a113afde24818101d37	Vendor (CNA)
Linux Linux	67bca5f1d644f4e79b694abd8052a177de81c37f	Vendor (CNA)
Linux Linux	981f339d2905b6a92ef59358158b326493aecac5	Vendor (CNA)
Linux Linux	c6ed54dd90698dc0744d669524cc1c122ded8a16	Vendor (CNA)
Linux Linux	c9115f49cf260d24d8b5f2d9a4b63cb31a627bb4	Vendor (CNA)
Linux Linux	cc2d2b3dbfb0ba57bc027fb7e1121250c50e4000	Vendor (CNA)
Linux Linux	d1308bd0b24cb1d78fa2747d5fa3e055cc628a48	Vendor (CNA)
Linux Linux	f748e15253833b771acbede14ea98f50831ac289	Vendor (CNA)
debian:linux	6.1.37-1 · Debian:12	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

SSVC exploitation— → noneOct 15, 2026, 11:07 PM UTC
Fix✗ → ✓Sep 28, 2026, 10:10 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/4e0473f1060aa49621d40a113afde24818101d37

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records