CVE-2024-50058: Linux kernel · serial: protect uart_port_dtr_rts() in uart_shutdown() too
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 5.5 Medium · fixed in 5.15.0-1080.87~20.04.1 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 23:28 UTC
- Patch
- Available – fixed in 5.15.0-1080.87~20.04.1, 5.15.0-1081.90~20.04.1, 5.15.0-1077.86~20.04.1 +62
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 21 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-7276-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7277-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7288-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7289-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7291-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7288-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7289-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7289-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7305-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7289-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-7308-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7310-1 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-6.11pkg:deb/ubuntu/linux-azure-6.11?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-nvidiapkg:deb/ubuntu/linux-azure-nvidia?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
In the Linux kernel, the following vulnerability has been resolved: serial: protect uart_port_dtr_rts() in uart_shutdown() too Commit af224ca2df29 (serial: core: Prevent unsafe uart port access, part 3) added few uport == NULL checks. It added one to uart_shutdown(), so the commit assumes, uport can be NULL in there. But right after that protection, there is an unprotected "uart_port_dtr_rts(uport, false);" call. That is invoked only if HUPCL is set, so I assume that is the reason why we do not see lots of these reports. Or it cannot be NULL at this point at all for some reason :P. Until the above is investigated, stay on the safe side and move this dereference to the if too. I got this inconsistency from Coverity under CID 1585130. Thanks.
References
- ubuntu.com/security/CVE-2024-50058 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2024-50058 (opens in a new tab)
- git.kernel.org/linus/602babaa84d627923713acaf5f7e9a4369e77473 (opens in a new tab)
- git.kernel.org/stable/c/e418d91195d29d5f9c9685ff309b92b04b41dc40 (opens in a new tab)
- git.kernel.org/stable/c/76ed24a34223bb2c6b6162e1d8389ec4e602a290 (opens in a new tab)
- git.kernel.org/stable/c/602babaa84d627923713acaf5f7e9a4369e77473 (opens in a new tab)
- ubuntu.com/security/notices/USN-7276-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7277-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7288-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7289-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7291-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7288-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7289-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7289-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7305-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7289-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-7308-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7310-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7331-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7383-1 (opens in a new tab)