Kernel memory corruption via double transport release
Published Dec 27, 2024 · Updated May 11, 2026
Use-after-free in the Linux kernel BFA SCSI driver allows local users to corrupt kernel memory during failed module loading. The bfad_init error path calls bfad_im_module_exit after bfad_im_module_init has already released the FC transport, releasing the same object twice. Administrative module-loading access and a BFA initialization failure are required; the demonstrated consequence is an invalid kernel-memory read.
Summary
What happened
Use-after-free in the Linux kernel BFA SCSI driver allows local users to corrupt kernel memory during failed module loading. The bfad_init error path calls bfad_im_module_exit after bfad_im_module_init has already released the FC transport, releasing the same object twice. Administrative module-loading access and a BFA initialization failure are required; the demonstrated consequence is an invalid kernel-memory read.
The record
- CVE
- CVE-2024-53227
- Published
- Dec 27, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Dec 27, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 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=2.6.32
- Affected versionversion=7725ccfda59715ecf8f99e3b520a0b84cc2ea79e <0ceac8012d3ddea3317f0d82934293d05feb8af1
- Affected versionversion=7725ccfda59715ecf8f99e3b520a0b84cc2ea79e <178b8f38932d635e90f5f0e9af1986c6f4a89271
- Affected versionversion=7725ccfda59715ecf8f99e3b520a0b84cc2ea79e <1ffdde30a90bf8efe8f270407f486706962b3292
- Affected versionversion=7725ccfda59715ecf8f99e3b520a0b84cc2ea79e <3932c753f805a02e9364a4c58b590f21901f8490
- Affected versionversion=7725ccfda59715ecf8f99e3b520a0b84cc2ea79e <8f5a97443b547b4c83f876f1d6a11df0f1fd4efb
- Affected versionversion=7725ccfda59715ecf8f99e3b520a0b84cc2ea79e <a2b5035ab0e368e8d8a371e27fbc72f133c0bd40
- Affected versionversion=7725ccfda59715ecf8f99e3b520a0b84cc2ea79e <c28409f851abd93b37969cac7498828ad533afd9
- Affected versionversion=7725ccfda59715ecf8f99e3b520a0b84cc2ea79e <e76181a5be90abcc3ed8a300bd13878aa214d022
- Affected versionversion=7725ccfda59715ecf8f99e3b520a0b84cc2ea79e <ef2c2580189ea88a0dcaf56eb3a565763a900edb
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