CVE-2024-58085

tomoyo: don't emit warning in tomoyo_write_control()

MEDIUM
5.5
CVSS Score
Published: March 6, 2025 at 04:22 PM UTC
Updated: October 15, 2026 at 02:17 AM UTC
2 products affected across 2 vendorsLinux KernelSIMATIC S7-1500 TM MFP

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 5.4.2915.11 ≤ v < 5.15.1795.16 ≤ v < 6.1.1295.5 ≤ v < 5.10.2356.13 ≤ v < 6.13.36.2 ≤ v < 6.6.786.7 ≤ v < 6.12.143.1bd03a3e4c9a9df0c6b007045fa7fc8889111a478
Vendor states this is fixed in 3df7546fc03b8f004eee0b9e3256369f7d096685 (fixed)
Vendor states this is fixed in 414705c0303350d139b1dc18f329fe47dfb642dd (fixed)
Vendor states this is fixed in a01c200fa7eb59da4d2dbbb48b61f4a0d196c09f (fixed)
Vendor states this is fixed in b2bd5857a0d6973ebbcb4d9831ddcaebbd257be1 (fixed)
Vendor states this is fixed in c67efabddc73171c7771d3ffe4ffa1e503ee533e (fixed)
Vendor states this is fixed in c9382f380e8d09209b8e5c0def0545852168be25 (fixed)
Vendor states this is fixed in f6b37b3e12de638753bce79a2858070b9c4a4ad3 (fixed)
Vendor states this is fixed in fe1c021eb03dae0dc9dce55e81f77a60e419a27a (fixed)
Vendor states this is fixed in 3.1 (unaffected)
Vendor states this is fixed in 5.10.235 (unaffected)
Vendor states this is fixed in 5.15.179 (unaffected)
Vendor states this is fixed in 5.4.291 (unaffected)
Vendor states this is fixed in 6.1.129 (unaffected)
Vendor states this is fixed in 6.12.14 (unaffected)
Vendor states this is fixed in 6.13.3 (unaffected)
Vendor states this is fixed in 6.14 (unaffected)
Vendor states this is fixed in 6.6.78 (unaffected)

References (11)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/3df7546fc03b8f004eee0b9e3256369f7d096685
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/414705c0303350d139b1dc18f329fe47dfb642dd
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/a01c200fa7eb59da4d2dbbb48b61f4a0d196c09f
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/b2bd5857a0d6973ebbcb4d9831ddcaebbd257be1
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/c67efabddc73171c7771d3ffe4ffa1e503ee533e
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/c9382f380e8d09209b8e5c0def0545852168be25
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/f6b37b3e12de638753bce79a2858070b9c4a4ad3
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/fe1c021eb03dae0dc9dce55e81f77a60e419a27a

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card