Kernel memory leak via failed ADC queue insertion
Published Oct 22, 2025 · Updated Oct 22, 2025
Memory leak in the Linux kernel PCF50633 ADC driver allows attackers to consume kernel memory via failed request queue insertion. The pcf50633_adc_async_read() function allocates a request, but it returns an adc_enqueue_request() failure without freeing the unqueued allocation. The public record does not specify how attackers can force the queue failure or whether repeated failures can interrupt service.
Summary
What happened
Memory leak in the Linux kernel PCF50633 ADC driver allows attackers to consume kernel memory via failed request queue insertion. The pcf50633_adc_async_read() function allocates a request, but it returns an adc_enqueue_request() failure without freeing the unqueued allocation. The public record does not specify how attackers can force the queue failure or whether repeated failures can interrupt service.
The record
- CVE
- CVE-2023-53724
- Published
- Oct 22, 2025
- Updated
- Oct 22, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 22, 2025CVE publishedPublication date reported by the CVE source.
- Oct 22, 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=08c3e06a5eb27d43b712adef18379f8464425e71 <3ee13bdf0d25ae8752ae6185b6d13bbb0d5a8e30
- Affected versionversion=08c3e06a5eb27d43b712adef18379f8464425e71 <41cdf082ae006ea002135dfaf43b2897de3bded8
- Affected versionversion=08c3e06a5eb27d43b712adef18379f8464425e71 <588edb4fb1f1e6487a0f60a5f7b9a24d2d0c9f8e
- Affected versionversion=08c3e06a5eb27d43b712adef18379f8464425e71 <66616eed76dfa6f3e442907760325a023c6da7e2
- Affected versionversion=08c3e06a5eb27d43b712adef18379f8464425e71 <6a8a02dcfae13ab07dc7bed2b409cec7f3d32e92
- Affected versionversion=08c3e06a5eb27d43b712adef18379f8464425e71 <8b450dcff23aa254844492831a8e2b508a9d522d
- Affected versionversion=08c3e06a5eb27d43b712adef18379f8464425e71 <9cca3a4933ca365cc664d5eefb0f942374ea8b41
- Affected versionversion=08c3e06a5eb27d43b712adef18379f8464425e71 <a62a5e79202967176a9c1a04e477860779accd6c
- Affected versionversion=2.6.29
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