mirror of
https://github.com/torvalds/linux.git
synced 2026-05-13 00:28:54 +02:00
901ac0ff15
Currently the runtime.oss.trigger field may be accessed concurrently without protection, which may lead to the data race. And, in this case, it may lead to more severe problem because it's a bit field; as writing the data, it may overwrite other bit fields as well, which confuses the operation completely, as spotted by fuzzing. Fix it by covering runtime.oss.trigger bit fled also with the existing params_lock mutex in both snd_pcm_oss_get_trigger() and snd_pcm_oss_poll(). Reported-and-tested-by: Jaeyoung Chung <jjy600901@snu.ac.kr> Closes: https://lore.kernel.org/20260423145330.210035-1-jjy600901@snu.ac.kr Cc: <stable@vger.kernel.org> Link: https://patch.msgid.link/20260424112205.123703-1-tiwai@suse.de Signed-off-by: Takashi Iwai <tiwai@suse.de> |
||
|---|---|---|
| .. | ||
| copy.c | ||
| io.c | ||
| linear.c | ||
| Makefile | ||
| mixer_oss.c | ||
| mulaw.c | ||
| pcm_oss.c | ||
| pcm_plugin.c | ||
| pcm_plugin.h | ||
| rate.c | ||
| route.c | ||