Kernel memory exhaustion via leaked NFC callback contexts
Published Sep 16, 2025 · Updated Sep 16, 2025
Memory leak in the Linux kernel NFC subsystem from 3.13 allows local users to exhaust kernel memory through secure-element I/O errors. The nfc_genl_se_io function allocates a callback context for APDU exchange, but several error paths neither arm bwi_timer to invoke se_io_cb nor free that context. Low-privileged local access to NFC secure-element I/O is required, and repeated failing requests can interrupt service by consuming kernel memory.
Summary
What happened
Memory leak in the Linux kernel NFC subsystem from 3.13 allows local users to exhaust kernel memory through secure-element I/O errors. The nfc_genl_se_io function allocates a callback context for APDU exchange, but several error paths neither arm bwi_timer to invoke se_io_cb nor free that context. Low-privileged local access to NFC secure-element I/O is required, and repeated failing requests can interrupt service by consuming kernel memory.
The record
- CVE
- CVE-2023-53298
- Published
- Sep 16, 2025
- Updated
- Sep 16, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 16, 2025CVE publishedPublication date reported by the CVE source.
- Sep 16, 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=3.13
- Affected versionversion=5ce3f32b5264b337bfd13a780452a17705307725 <25ff6f8a5a3b8dc48e8abda6f013e8cc4b14ffea
- Affected versionversion=5ce3f32b5264b337bfd13a780452a17705307725 <271eed1736426103335c5aac50f15b0f4d236bc0
- Affected versionversion=5ce3f32b5264b337bfd13a780452a17705307725 <5321da6d84b87a34eea441677d649c34bd854169
- Affected versionversion=5ce3f32b5264b337bfd13a780452a17705307725 <8978315cb4bf8878c9c8ec05dafd8f7ff539860d
- Affected versionversion=5ce3f32b5264b337bfd13a780452a17705307725 <af452e35b9e6a87cd49e54a7a3d60d934b194651
- Affected versionversion=5ce3f32b5264b337bfd13a780452a17705307725 <b2036a252381949d3b743a3de069324ae3028a57
- Affected versionversion=5ce3f32b5264b337bfd13a780452a17705307725 <ba98db08895748c12e5ded52cd1598dce2c79e55
- Affected versionversion=5ce3f32b5264b337bfd13a780452a17705307725 <c494365432dcdc549986f4d9af9eb6190cbdb153
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