Kernel memory leak via failed interrupt binding
Published Dec 24, 2025 · Updated Dec 24, 2025
A memory leak in affected Linux kernel branches from 2.6.27 consumes memory when x86 Xen CPU lock interrupt-handler binding fails. xen_init_lock_cpu allocates the handler name with kasprintf but returns without freeing it when bind_ipi_to_irqhandler fails. Exposure is limited to the x86 Xen initialization path, and public sources establish neither attacker control of the failure nor service interruption.
Summary
What happened
A memory leak in affected Linux kernel branches from 2.6.27 consumes memory when x86 Xen CPU lock interrupt-handler binding fails. xen_init_lock_cpu allocates the handler name with kasprintf but returns without freeing it when bind_ipi_to_irqhandler fails. Exposure is limited to the x86 Xen initialization path, and public sources establish neither attacker control of the failure nor service interruption.
The record
- CVE
- CVE-2022-50761
- 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=2.6.27
- Affected versionversion=2d9e1e2f58b5612aa4eab0ab54c84308a29dbd79 <07764d00c869a3390bd4f80412cc8b0e669e6c58
- Affected versionversion=2d9e1e2f58b5612aa4eab0ab54c84308a29dbd79 <29198f667f4486f9e227e11faf1411fcf4c82a66
- Affected versionversion=2d9e1e2f58b5612aa4eab0ab54c84308a29dbd79 <53ff99c76be611acea37d33133c9136969914865
- Affected versionversion=2d9e1e2f58b5612aa4eab0ab54c84308a29dbd79 <70966d6b0f59f795b08a70adf5e4478348ecbfbb
- Affected versionversion=2d9e1e2f58b5612aa4eab0ab54c84308a29dbd79 <70e7f308d7a8e915c7fbc0f1d959968eab8000cd
- Affected versionversion=2d9e1e2f58b5612aa4eab0ab54c84308a29dbd79 <798fc3cf98ca07e448956f39295c5d686ab4b054
- Affected versionversion=2d9e1e2f58b5612aa4eab0ab54c84308a29dbd79 <9278bdbb566656b3704704f8dd6cbc24a6fcc569
- Affected versionversion=2d9e1e2f58b5612aa4eab0ab54c84308a29dbd79 <b44457b83a034efef58ffa5f3131d4615f1a9837
- Affected versionversion=2d9e1e2f58b5612aa4eab0ab54c84308a29dbd79 <ca84ce153d887b1dc8b118029976cc9faf2a9b40
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