Kernel memory corruption via concurrent TOMOYO writes
Published Mar 4, 2024 · Updated May 11, 2026
Use-after-free in TOMOYO policy control in Linux allows local users to corrupt kernel memory through concurrent long-line writes. tomoyo_write_control() reads head->write_buf before taking head->io_sem, while another writer can replace and free that buffer, leading to a stale-buffer write and double free. Exploitation requires write access to a TOMOYO control file and overlapping writes; successful triggering can corrupt kernel memory or crash the system.
Summary
What happened
Use-after-free in TOMOYO policy control in Linux allows local users to corrupt kernel memory through concurrent long-line writes. tomoyo_write_control() reads head->write_buf before taking head->io_sem, while another writer can replace and free that buffer, leading to a stale-buffer write and double free. Exploitation requires write access to a TOMOYO control file and overlapping writes; successful triggering can corrupt kernel memory or crash the system.
The record
- CVE
- CVE-2024-26622
- Published
- Mar 4, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 4, 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=3.1
- Affected versionversion=bd03a3e4c9a9df0c6b007045fa7fc8889111a478 <2caa605079488da9601099fbda460cfc1702839f
- Affected versionversion=bd03a3e4c9a9df0c6b007045fa7fc8889111a478 <2f03fc340cac9ea1dc63cbf8c93dd2eb0f227815
- Affected versionversion=bd03a3e4c9a9df0c6b007045fa7fc8889111a478 <3bfe04c1273d30b866f4c7c238331ed3b08e5824
- Affected versionversion=bd03a3e4c9a9df0c6b007045fa7fc8889111a478 <6edefe1b6c29a9932f558a898968a9fcbeec5711
- Affected versionversion=bd03a3e4c9a9df0c6b007045fa7fc8889111a478 <7d930a4da17958f869ef679ee0e4a8729337affc
- Affected versionversion=bd03a3e4c9a9df0c6b007045fa7fc8889111a478 <a23ac1788e2c828c097119e9a3178f0b7e503fee
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