Kernel memory corruption via stale bfad pointer
Published Sep 4, 2025 · Updated May 12, 2026
Double free in the bfa SCSI driver in Linux and SIMATIC CN 4100 before V5.0 allows local users to corrupt kernel memory. On an initialization error, bfad_im_probe() frees bfad->im but leaves the stale pointer set, so bfad_im_probe_undo() frees the allocation again when bfad_sm_stopping runs. The path requires local administrative control to uninstall the driver after the failed probe; published sources document the double free but no demonstrated post-free exploit.
Summary
What happened
Double free in the bfa SCSI driver in Linux and SIMATIC CN 4100 before V5.0 allows local users to corrupt kernel memory. On an initialization error, bfad_im_probe() frees bfad->im but leaves the stale pointer set, so bfad_im_probe_undo() frees the allocation again when bfad_sm_stopping runs. The path requires local administrative control to uninstall the driver after the failed probe; published sources document the double free but no demonstrated post-free exploit.
The record
- CVE
- CVE-2025-38699
- Published
- Sep 4, 2025
- Updated
- May 12, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-415
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 4, 2025CVE publishedPublication date reported by the CVE source.
- May 12, 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 <13f613228cf3c96a038424cd97aa4d6aadc66294
- Affected versionversion=7725ccfda59715ecf8f99e3b520a0b84cc2ea79e <39cfe2c83146aad956318f866d0ee471b7a61fa5
- Affected versionversion=7725ccfda59715ecf8f99e3b520a0b84cc2ea79e <50d9bd48321038bd6e15af5a454bbcd180cf6f80
- Affected versionversion=7725ccfda59715ecf8f99e3b520a0b84cc2ea79e <684c92bb08a25ed3c0356bc7eb532ed5b19588dd
- Affected versionversion=7725ccfda59715ecf8f99e3b520a0b84cc2ea79e <8456f862cb95bcc3a831e1ba87c0c17068be0f3f
- Affected versionversion=7725ccfda59715ecf8f99e3b520a0b84cc2ea79e <8e03dd9fadf76db5b9799583074a1a2a54f787f1
- Affected versionversion=7725ccfda59715ecf8f99e3b520a0b84cc2ea79e <9337c2affbaebe00b75fdf84ea0e2fcf93c140af
- Affected versionversion=7725ccfda59715ecf8f99e3b520a0b84cc2ea79e <add4c4850363d7c1b72e8fce9ccb21fdd2cf5dc9
- Affected versionversion=7725ccfda59715ecf8f99e3b520a0b84cc2ea79e <ba024d92564580bb90ec367248ace8efe16ce815
What conditions does exploitation require?
What is affected?
Published CVSS scores
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
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