CVE-2024-26622

What it is

In the Linux kernel, the following vulnerability has been resolved: tomoyo: fix UAF write bug in tomoyo_write_control() Since tomoyo_write_control() updates head->write_buf when write() of long lines is requested, we need to fetch head->write_buf after head->io_sem is held. Otherwise, concurrent write() requests can cause use-after-free-write and double-free problems.

At a glance

Exploitability

Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.

Exploit odds

0.2% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2024-03-04 07:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 07:17 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.2% in the next 30 days (EPSS).
• Severity: 7.8 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2024-03-04 07:15 UTC

Last modified

2026-06-17 07:17 UTC

Exploit probability

0.2% · EPSS, next 30 days

Weakness

CWE-416 · Use after free

Record status

Modified

Affected

• Linux Kernel < 5.10.212
• Linux Kernel < 5.15.151
• Linux Kernel < 6.1.81
• Linux Kernel < 6.6.21
• Linux Kernel < 6.7.9
• Linux Kernel 6.8

Attack profile CVSS 3.1 · 7.8

Attack vector

Local

Complexity

Low

Privileges needed

Low

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2024-26622.md and follow it. Check whether this project is affected by CVE-2024-26622. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge