CVE-2024-50058

serial: protect uart_port_dtr_rts() in uart_shutdown() too

MEDIUM
5.5
CVSS Score
Published: October 21, 2024 at 07:39 PM UTC
Updated: October 15, 2026 at 01:19 AM UTC
2 products affected across 2 vendorsLinux KernelSIMATIC S7-1500 TM MFP

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

All versionsv < 6.6.576.7 ≤ v < 6.11.44.7af224ca2df297440448b9d407d21b50982c6d532
Vendor states this is fixed in 2fe399bb8efd0d325ab1138cf8e3ecf23a39e96d (fixed)
Vendor states this is fixed in 399927f0f875b93f3d5a0336d382ba48b8671eb2 (fixed)
Vendor states this is fixed in 602babaa84d627923713acaf5f7e9a4369e77473 (fixed)
Vendor states this is fixed in 76ed24a34223bb2c6b6162e1d8389ec4e602a290 (fixed)
Vendor states this is fixed in d7b5876a6e74cdf8468a478be6b23f2f5464ac7a (fixed)
Vendor states this is fixed in e418d91195d29d5f9c9685ff309b92b04b41dc40 (fixed)
Vendor states this is fixed in 4.7 (unaffected)
Vendor states this is fixed in 5.10.229 (unaffected)
Vendor states this is fixed in 5.15.170 (unaffected)
Vendor states this is fixed in 6.1.115 (unaffected)
Vendor states this is fixed in 6.11.4 (unaffected)
Vendor states this is fixed in 6.12 (unaffected)
Vendor states this is fixed in 6.6.57 (unaffected)

References (9)

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-476

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card