Service degradation via SNIC device-name memory leak
Published Sep 18, 2025 · Updated Sep 18, 2025
Memory leak in the Linux kernel SNIC SCSI driver 4.2 through 6.4.10 allows local users to degrade service through device-addition failures. In snic_tgt_create(), dev_set_name() allocates a device name, but the device_add() error path omits put_device(), so kobject cleanup cannot release the name. Exploitation requires local low-privileged access and a SNIC target-addition failure; repeated failures consume kernel memory without affecting confidentiality or integrity.
Summary
What happened
Memory leak in the Linux kernel SNIC SCSI driver 4.2 through 6.4.10 allows local users to degrade service through device-addition failures. In snic_tgt_create(), dev_set_name() allocates a device name, but the device_add() error path omits put_device(), so kobject cleanup cannot release the name. Exploitation requires local low-privileged access and a SNIC target-addition failure; repeated failures consume kernel memory without affecting confidentiality or integrity.
The record
- CVE
- CVE-2023-53436
- Published
- Sep 18, 2025
- Updated
- Sep 18, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 18, 2025CVE publishedPublication date reported by the CVE source.
- Sep 18, 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=4.2
- Affected versionversion=c8806b6c9e824f47726f2a9b7fbbe7ebf19306fa <41320b18a0e0dfb236dba4edb9be12dba1878156
- Affected versionversion=c8806b6c9e824f47726f2a9b7fbbe7ebf19306fa <461f8ac666fa232afee5ed6420099913ec4e4ba2
- Affected versionversion=c8806b6c9e824f47726f2a9b7fbbe7ebf19306fa <58889d5ad74cbc1c9595db74e13522b58b69b0ec
- Affected versionversion=c8806b6c9e824f47726f2a9b7fbbe7ebf19306fa <7723a5d5d187626c4c640842e522cf4e9e39492e
- Affected versionversion=c8806b6c9e824f47726f2a9b7fbbe7ebf19306fa <789275f7c0544374d40bc8d9c81f96751a41df45
- Affected versionversion=c8806b6c9e824f47726f2a9b7fbbe7ebf19306fa <cea09922f5f75652d55b481ee34011fc7f19868b
- Affected versionversion=c8806b6c9e824f47726f2a9b7fbbe7ebf19306fa <ed0acb1ee2e9322b96611635a9ca9303d15ac76c
- Affected versionversion=c8806b6c9e824f47726f2a9b7fbbe7ebf19306fa <f830968d464f55e11bc9260a132fc77daa266aa3
What conditions does exploitation require?
What is affected?
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