tomoyo: don't emit warning in tomoyo_write_control()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ bd03a3e4c9a9df0c6b007045fa7fc8889111a478 · < c9382f380e8d09209b8e5c0def0545852168be25| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's TOMOYO control-write function can emit an oversized-allocation warning when it receives a very long line without a newline. Triggering it requires the ability to write to the TOMOYO control interface; the input does not specify whether authentication is required.
Engineers running Linux kernels with TOMOYO should check their kernel versions against the vendor advisory; affected versions are not specified in the input.