CVE-2024-43893: serial: core: check uartclk for zero to avoid divide by zero
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
Security readout for executives and security teams
Plain-English summary
CVE-2024-43893 is a Linux kernel stability flaw in serial port handling. A local action using invalid serial settings can make the kernel divide by zero, causing an Oops and potential denial of service. The source bundle does not show remote exploitation, privilege escalation, CVSS scoring, or confirmed active exploitation.
Executive priority
Treat as a moderate Linux kernel availability issue. Patch through normal kernel maintenance, faster for multi-user, embedded, industrial, or appliance environments with serial interfaces. No source evidence supports emergency internet-wide response.
Technical view
The Linux serial core did not reject a zero uartclk early enough when TIOCSSERIAL supplied an invalid baud_base. Later termios processing reached uart_get_divisor() and divided by zero. Kernel stable commits add the missing check before applying other serial settings.
Likely exposure
Exposure is most relevant on Linux systems where users, services, containers, or device-management software can interact with serial TTY ioctls. Servers without accessible serial devices are likely lower risk. Siemens and Debian references show downstream tracking, so embedded and appliance fleets should verify vendor kernels.
Exploitation context
The bundle supports a local denial-of-service interpretation through ioctl-triggered kernel Oops. KEV is false, and no provided source states active exploitation or public weaponization. Required permissions and device access are not fully established in the supplied evidence.
Researcher notes
Key uncertainty is exploitability conditions around who can invoke TIOCSSERIAL on relevant ports. The root cause and fix location are clear from the kernel description and stable commits, but the bundle lacks CVSS, CWE, privilege requirements, or proof of exploitation.
Mitigation direction
Apply Linux kernel updates containing the referenced stable serial-core fixes.
Use distribution security updates, including Debian LTS advisories where applicable.
Check Siemens ProductCERT guidance for affected Siemens products and fixed firmware.
Restrict unnecessary local access to serial devices until patched.
Prioritize systems where untrusted users or services can access TTY devices.
Validation and detection
Inventory running kernel versions and vendor kernel package revisions.
Check vendor advisories for CVE-2024-43893 coverage and fixed package versions.
Confirm kernel changelogs include the serial core uartclk zero check.
Review device permissions for serial TTY exposure to untrusted accounts.
After patching, verify updated kernels are booted, not merely installed.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-43893 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.