serial: core: check uartclk for zero to avoid divide by zero
- 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 4.19.320, 5.4.282, 5.10.224, 5.15.165, 6.1.105, 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
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: serial: core: check uartclk for zero to avoid divide by zero Calling ioctl TIOCSSERIAL with an invalid baud_base can result in uartclk being zero, which will result in a divide by zero error in uart_get_divisor(). The check for uartclk being zero in uart_set_info() needs to be done before other settings are made as subsequent calls to ioctl TIOCSSERIAL for the same port would be impacted if the uartclk check was done where uartclk gets set. Oops: divide error: 0000 PREEMPT SMP KASAN PTI RIP: 0010:uart_get_divisor (drivers/tty/serial/serial_core.c:580) Call Trace: <TASK> serial8250_get_divisor (drivers/tty/serial/8250/8250_port.c:2576 drivers/tty/serial/8250/8250_port.c:2589) serial8250_do_set_termios (drivers/tty/serial/8250/8250_port.c:502 drivers/tty/serial/8250/8250_port.c:2741) serial8250_set_termios (drivers/tty/serial/8250/8250_port.c:2862) uart_change_line_settings (./include/linux/spinlock.h:376 ./include/linux/serial_core.h:608 drivers/tty/serial/serial_core.c:222) uart_port_startup (drivers/tty/serial/serial_core.c:342) uart_startup (drivers/tty/serial/serial_core.c:368) uart_set_info (drivers/tty/serial/serial_core.c:1034) uart_set_info_user (drivers/tty/serial/serial_core.c:1059) tty_set_serial (drivers/tty/tty_io.c:2637) tty_ioctl (drivers/tty/tty_io.c:2647 drivers/tty/tty_io.c:2791) __x64_sys_ioctl (fs/ioctl.c:52 fs/ioctl.c:907 fs/ioctl.c:893 fs/ioctl.c:893) do_syscall_64 (arch/x86/entry/common.c:52 (discriminator 1) arch/x86/entry/common.c:83 (discriminator 1)) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130) Rule: add
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 3bbd90fca824e6fd61fb20f6dd2b0fa5f8b14bba; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 55b2a5d331a6ceb1c4372945fdb77181265ba24f; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 52b138f1021113e593ee6ad258ce08fe90693a9e; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 9196e42a3b8eeff1707e6ef769112b4b6096be49; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in e13ba3fe5ee070f8a9dab60029d52b1f61da5051; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in e3ad503876283ac3fcca922a1bf243ef9eb0b0e2; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 68dc02f319b9ee54dc23caba742a5c754d1cccc8; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 6eabce6608d6f3440f4c03aa3d3ef50a47a3d193
- Linux Linux
2.6.12
- KernelLinux
From 2.6.12 · fixed in 4.19.320; From 4.20.0 · fixed in 5.4.282; From 5.5.0 · fixed in 5.10.224; From 5.11.0 · fixed in 5.15.165; From 5.16.0 · fixed in 6.1.105; From 6.2.0 · fixed in 6.6.46; From 6.7.0 · fixed in 6.10.5
References 8
git.kernel.org
- stable/c/3bbd90fca824e6fd61fb20f6dd2b0fa5f8b14bba
- stable/c/55b2a5d331a6ceb1c4372945fdb77181265ba24f
- stable/c/52b138f1021113e593ee6ad258ce08fe90693a9e
- stable/c/9196e42a3b8eeff1707e6ef769112b4b6096be49
- stable/c/e13ba3fe5ee070f8a9dab60029d52b1f61da5051
- stable/c/e3ad503876283ac3fcca922a1bf243ef9eb0b0e2
- stable/c/68dc02f319b9ee54dc23caba742a5c754d1cccc8
- stable/c/6eabce6608d6f3440f4c03aa3d3ef50a47a3d193