Kernel panic via uncanceled hfi1 counter work
Published Oct 1, 2025 · Updated Oct 1, 2025
Use-after-free in the Linux kernel hfi1 driver from 4.3 allows local users with administrative capabilities to panic the system. During hot-unplug or driver removal, queued update_cntr_work can execute after device teardown frees its backing memory because hfi1 did not synchronously cancel the work first. Reaching the race requires an hfi1 device and administrative ability to hot-unplug, unbind, or remove its driver; the reported consequence is an availability-only kernel panic.
Summary
What happened
Use-after-free in the Linux kernel hfi1 driver from 4.3 allows local users with administrative capabilities to panic the system. During hot-unplug or driver removal, queued update_cntr_work can execute after device teardown frees its backing memory because hfi1 did not synchronously cancel the work first. Reaching the race requires an hfi1 device and administrative ability to hot-unplug, unbind, or remove its driver; the reported consequence is an availability-only kernel panic.
The record
- CVE
- CVE-2023-53488
- Published
- Oct 1, 2025
- Updated
- Oct 1, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-664, T1499
- Attack vector
- local
- Privileges
- admin
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=4.3
- Affected versionversion=7724105686e718ac476a6ad3304fea2fbcfcffde <33c677d1e087e437c7dcaad8d73402cf6add282e
- Affected versionversion=7724105686e718ac476a6ad3304fea2fbcfcffde <4fdfaef71fced490835145631a795497646f4555
- Affected versionversion=7724105686e718ac476a6ad3304fea2fbcfcffde <5e72f33ddfdb69cb21c1b59d31bbd3498d31b14a
- Affected versionversion=7724105686e718ac476a6ad3304fea2fbcfcffde <918c1e6843b7e81d0e5cf7994f41f28dc34c98b0
- Affected versionversion=7724105686e718ac476a6ad3304fea2fbcfcffde <ac6640f4193d0f5b44269a7f08372909f9a18e5c
- Affected versionversion=7724105686e718ac476a6ad3304fea2fbcfcffde <bfd727ad8411995218f336ead9f2becfde7f3a89
- Affected versionversion=7724105686e718ac476a6ad3304fea2fbcfcffde <c2145b18740c7e697748e4005ce93a5c683c86a8
- Affected versionversion=7724105686e718ac476a6ad3304fea2fbcfcffde <d32a5e9b825d40c08a43dfbcba007159fed41a5d
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.
Weakness, pattern, technique
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