# CVE-2024-58085: tomoyo: don't emit warning in tomoyo_write_control()

> A local attacker can trigger a kernel warning and potential resource exhaustion by writing excessively long lines to the TOMOYO control interface.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Mar 2025
- **Updated:** 15 Oct 2026
- **Also known as:** BELL-CVE-2024-58085, DEBIAN-CVE-2024-58085, GHSA-hr43-3hq8-ggg4, ROOT-OS-UBUNTU-2404-CVE-2024-58085, UBUNTU-CVE-2024-58085

## What is CVE-2024-58085?

CVE-2024-58085 is a medium-severity denial of service vulnerability in Linux kernel, published on 6 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

tomoyo: don't emit warning in tomoyo_write_control()

syzbot is reporting too large allocation warning at tomoyo_write_control(),
for one can write a very very long line without new line character. To fix
this warning, I use __GFP_NOWARN rather than checking for KMALLOC_MAX_SIZE,
for practically a valid line should be always shorter than 32KB where the
"too small to fail" memory-allocation rule applies.

One might try to write a valid line that is longer than 32KB, but such
request will likely fail with -ENOMEM. Therefore, I feel that separately
returning -EINVAL when a line is longer than KMALLOC_MAX_SIZE is redundant.
There is no need to distinguish over-32KB and over-KMALLOC_MAX_SIZE.

## Which versions are affected by CVE-2024-58085?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2024-58085?

Apply the vendor's patch.

## Is CVE-2024-58085 being exploited?

There is no known exploitation of CVE-2024-58085 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-58085 and fix it if it is affected.

What it is: CVE-2024-58085 is a medium-severity denial of service vulnerability in Linux kernel, published on 6 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-58085 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-58085/ (Markdown: https://insights.sbomify.com/CVE-2024-58085/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-58085
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-58085
- OSV: https://osv.dev/vulnerability/CVE-2024-58085

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-58085/
Summaries are generated and may contain mistakes; the official description above is the record.