Kernel memory consumption via unreleased autofs waitqueues
Published Dec 24, 2025 · Updated Dec 24, 2025
Memory leak in Linux autofs 2.6.27 and later allows attackers to consume kernel memory via interrupted expiration waits. autofs_catatonic_mode decrements a waitqueue's wait_ctr to zero after an interrupted autofs_wait but fails to free that queue, losing its 96-byte allocation. The published record does not establish an attacker privilege level; the demonstrated consequence is loss of one 96-byte kernel allocation per affected queue.
Summary
What happened
Memory leak in Linux autofs 2.6.27 and later allows attackers to consume kernel memory via interrupted expiration waits. autofs_catatonic_mode decrements a waitqueue's wait_ctr to zero after an interrupted autofs_wait but fails to free that queue, losing its 96-byte allocation. The published record does not establish an attacker privilege level; the demonstrated consequence is loss of one 96-byte kernel allocation per affected queue.
The record
- CVE
- CVE-2023-54134
- Published
- Dec 24, 2025
- Updated
- Dec 24, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 24, 2025CVE publishedPublication date reported by the CVE source.
- Dec 24, 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 <1985e8eae8627f02e3364690c5fed7af1c46be55
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6079dc77c6f32936e8a6766ee8334ae3c99f4504
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <696b625f3f85d80fca48c24d2948fbc451e74366
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <69ddafc7a7afd8401bab53eff5af813fa0d368a2
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <71eeddcad7342292c19042c290c477697acaccab
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <726deae613bc1b6096ad3b61cc1e63e33330fbc2
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <976abbdc120a97049b9133e60fa7b29627d11de4
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ccbe77f7e45dfb4420f7f531b650c00c6e9c7507
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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
No sourced classifications are available.
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