CVE-2024-50058

Source
https://cve.org/CVERecord?id=CVE-2024-50058
Import Source
https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2024-50058.json
JSON Data
https://api.test.osv.dev/v1/vulns/CVE-2024-50058
Downstream
Related
Published
2024-10-21T19:39:48.420Z
Modified
2026-03-20T12:39:33.639754Z
Summary
serial: protect uart_port_dtr_rts() in uart_shutdown() too
Details

In the Linux kernel, the following vulnerability has been resolved:

serial: protect uartportdtrrts() in uartshutdown() too

Commit af224ca2df29 (serial: core: Prevent unsafe uart port access, part 3) added few uport == NULL checks. It added one to uartshutdown(), so the commit assumes, uport can be NULL in there. But right after that protection, there is an unprotected "uartportdtrrts(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.

Database specific
{
    "cna_assigner": "Linux",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/50xxx/CVE-2024-50058.json"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
af224ca2df297440448b9d407d21b50982c6d532
Fixed
2fe399bb8efd0d325ab1138cf8e3ecf23a39e96d
Fixed
399927f0f875b93f3d5a0336d382ba48b8671eb2
Fixed
d7b5876a6e74cdf8468a478be6b23f2f5464ac7a
Fixed
e418d91195d29d5f9c9685ff309b92b04b41dc40
Fixed
76ed24a34223bb2c6b6162e1d8389ec4e602a290
Fixed
602babaa84d627923713acaf5f7e9a4369e77473

Database specific

source
"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2024-50058.json"