tomoyo: don't emit warning in tomoyo_write_control()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.4.291, 5.10.235, 5.15.179, 6.1.129, 6.6.78, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux 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 Linux
3.1
- KernelLinux
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
References 8
git.kernel.org
- stable/c/c67efabddc73171c7771d3ffe4ffa1e503ee533e
- stable/c/f6b37b3e12de638753bce79a2858070b9c4a4ad3
- stable/c/b2bd5857a0d6973ebbcb4d9831ddcaebbd257be1
- stable/c/a01c200fa7eb59da4d2dbbb48b61f4a0d196c09f
- stable/c/fe1c021eb03dae0dc9dce55e81f77a60e419a27a
- stable/c/c9382f380e8d09209b8e5c0def0545852168be25
- stable/c/414705c0303350d139b1dc18f329fe47dfb642dd
- stable/c/3df7546fc03b8f004eee0b9e3256369f7d096685