mirror of
https://github.com/torvalds/linux.git
synced 2026-09-14 16:10:02 +02:00
vt: add mode validation in vt_setactivate
The vt_setactivate() function accepts any mode value without validation, while VT_SETMODE correctly rejects invalid values (only VT_AUTO and VT_PROCESS are valid). This allows users to set invalid mode values (e.g., 0xFF) which bypasses VT_PROCESS signal handling and causes undefined VT switching behavior. Fix this by adding the same validation as VT_SETMODE. Signed-off-by: Wang Zihan <jiyu03@qq.com> Link: https://patch.msgid.link/tencent_6A7DAE2E1288663D23AACBE2950D6E535007@qq.com Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
This commit is contained in:
parent
8200871327
commit
e62745dd11
|
|
@ -596,6 +596,8 @@ static int vt_setactivate(struct vt_setactivate __user *sa)
|
|||
return -EFAULT;
|
||||
if (vsa.console == 0 || vsa.console > MAX_NR_CONSOLES)
|
||||
return -ENXIO;
|
||||
if (vsa.mode.mode != VT_AUTO && vsa.mode.mode != VT_PROCESS)
|
||||
return -EINVAL;
|
||||
|
||||
vsa.console--;
|
||||
vsa.console = array_index_nospec(vsa.console, MAX_NR_CONSOLES);
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user