Kernel code execution via stale CPU rmap pointer
Published Oct 1, 2025 · Updated Oct 1, 2025
Use-after-free in the Linux kernel CPU rmap from 3.8 through 6.3 allows local users with CAP_NET_ADMIN to execute kernel code. When irq_set_affinity_notifier clears a notifier, irq_cpu_rmap_remove frees its glue object but leaves the pointer in rmap->obj, and free_irq_cpu_rmap later dereferences the stale entry. Exploitation requires local control of affected network-device configuration and teardown paths; successful reuse can disclose or modify kernel memory or panic the host.
Summary
What happened
Use-after-free in the Linux kernel CPU rmap from 3.8 through 6.3 allows local users with CAP_NET_ADMIN to execute kernel code. When irq_set_affinity_notifier clears a notifier, irq_cpu_rmap_remove frees its glue object but leaves the pointer in rmap->obj, and free_irq_cpu_rmap later dereferences the stale entry. Exploitation requires local control of affected network-device configuration and teardown paths; successful reuse can disclose or modify kernel memory or panic the host.
The record
- CVE
- CVE-2023-53484
- Published
- Oct 1, 2025
- Updated
- Oct 1, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 1, 2025CVE publishedPublication date reported by the CVE source.
- Oct 1, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <4e0473f1060aa49621d40a113afde24818101d37
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <67bca5f1d644f4e79b694abd8052a177de81c37f
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <981f339d2905b6a92ef59358158b326493aecac5
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c6ed54dd90698dc0744d669524cc1c122ded8a16
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c9115f49cf260d24d8b5f2d9a4b63cb31a627bb4
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <cc2d2b3dbfb0ba57bc027fb7e1121250c50e4000
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d1308bd0b24cb1d78fa2747d5fa3e055cc628a48
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f748e15253833b771acbede14ea98f50831ac289
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo