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 tomoyowritecontrol()
syzbot is reporting too large allocation warning at tomoyowritecontrol(), for one can write a very very long line without new line character. To fix this warning, I use GFPNOWARN rather than checking for KMALLOCMAXSIZE, 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 KMALLOCMAXSIZE is redundant. There is no need to distinguish over-32KB and over-KMALLOCMAXSIZE.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2024-58085?
CVE-2024-58085 has been classified as a low severity vulnerability due to its specific conditions and impact.
How do I fix CVE-2024-58085?
To fix CVE-2024-58085, update the Linux kernel to the patched version as released by the maintainers.
Which versions of the Linux kernel are affected by CVE-2024-58085?
CVE-2024-58085 affects specific versions of the Linux kernel prior to the fix that resolves the warning in tomoyo_write_control().
What is the primary impact of CVE-2024-58085?
The primary impact of CVE-2024-58085 is an inappropriate warning message generated when writing excessively long lines in tomoyo_write_control().
Is CVE-2024-58085 remotely exploitable?
CVE-2024-58085 is not considered remotely exploitable as it requires local access to the affected system.