CVE-2024-58085: tomoyo: don't emit warning in tomoyo_write_control()
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.
Security readout for executives and security teams
Plain-English summary
CVE-2024-58085 is a Linux kernel TOMOYO issue where an extremely long control-line input could trigger a large-allocation warning. The public record describes a kernel fix, not a data theft, remote compromise, or privilege escalation path. Business urgency depends on whether affected kernels are deployed and TOMOYO is in use.
Executive priority
Treat this as a kernel hygiene item, not an emergency, unless critical systems run affected kernels with TOMOYO exposed. Prioritize normal patch cycles, with higher urgency for internet-facing or vendor-managed appliances where kernel posture is hard to verify.
Technical view
The issue is in tomoyo_write_control(). The kernel CVE text says syzbot reported a too-large allocation warning when a line without a newline is very long. Stable fixes use __GFP_NOWARN and note very large valid lines will likely fail with -ENOMEM.
Likely exposure
Exposure is likely limited to Linux systems running affected kernel versions with TOMOYO enabled and its control path reachable. The bundle lists Linux kernel versions and stable commit references but does not provide distribution-specific affected matrices beyond Debian advisories.
Exploitation context
No cited source states active exploitation, and the record is not marked CISA KEV. The available evidence describes a robustness fix for oversized input handling, not a confirmed weaponized attack path. Access prerequisites and practical impact are not fully documented in the bundle.
Researcher notes
The source bundle lacks CVSS, CWE, exploitability details, and complete access requirements. Avoid assuming remote reachability or privilege escalation. Focus validation on kernel version, TOMOYO configuration, downstream vendor advisories, and whether the stable fix commits are present.
Mitigation direction
Apply vendor kernel updates that include the referenced stable fixes.
Check Debian LTS advisories if using affected Debian kernels.
Review Siemens guidance if using affected Siemens products.
Confirm TOMOYO exposure and configuration on Linux hosts.
If no vendor fix is available, follow vendor guidance for temporary risk reduction.
Validation and detection
Inventory Linux kernel versions across servers, appliances, and containers hosts.
Map kernel builds against the CVE affected version list and stable commits.
Check whether TOMOYO is enabled in deployed kernels.
Verify vendor packages include the referenced upstream fixes.
Document systems pending reboot after kernel update.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-58085 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
2ADP providers
12Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Mar 6, 2025, 16:22 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.