Memory leak via skipped probe cleanup
Published Feb 14, 2026 · Updated Feb 14, 2026
A memory leak in the Tegra SLINK SPI probe path in affected Linux Kernel branches leaves probe resources unreleased after IRQ lookup fails. tegra_slink_probe() returns immediately when platform_get_irq() fails instead of taking the exit_pm_put cleanup path. The failure must occur while the Tegra SLINK controller is being probed; published sources identify no attacker-controlled trigger or service-level consequence.
Summary
What happened
A memory leak in the Tegra SLINK SPI probe path in affected Linux Kernel branches leaves probe resources unreleased after IRQ lookup fails. tegra_slink_probe() returns immediately when platform_get_irq() fails instead of taking the exit_pm_put cleanup path. The failure must occur while the Tegra SLINK controller is being probed; published sources identify no attacker-controlled trigger or service-level consequence.
The record
- CVE
- CVE-2026-23182
- Published
- Feb 14, 2026
- Updated
- Feb 14, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Feb 14, 2026CVE publishedPublication date reported by the CVE source.
- Feb 14, 2026Record 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=46ee23101f32a1ced5335d5407d5ecffd160ccdf <126a09f4fcd2b895a818ca43fde078d907c1ac9a
- Affected versionversion=4eb8065494ca19caba3f45fc83941fd568a8c3cd
- Affected versionversion=5c25f89c00b97844d0427f0f96818a15714bd609 <327b71326cc1834bc031e8f52a470a18dfd9caa6
- Affected versionversion=6.7
- Affected versionversion=b64683f5d7282f7b160e9867e33cdac00b5c792b <6a04dc650cef8d52a1ccb4ae245dbe318ffff32e
- Affected versionversion=eb9913b511f10968a02cfa5329a896855dd152a3 <075415ae18b5b3e4d0187962d538653154216fe7
- Affected versionversion=eb9913b511f10968a02cfa5329a896855dd152a3 <41d9a6795b95d6ea28439ac1e9ce8c95bbca20fc
- Affected versionversion=eb9913b511f10968a02cfa5329a896855dd152a3 <b8eec12aa666c11f8a6ad1488c568f85c58875fa
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