CVE-2024-50058: serial: protect uart_port_dtr_rts() in uart_shutdown() too
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 2fe399bb8efd0d325ab1138cf8e3ecf23a39e96d, 399927f0f875b93f3d5a0336d382ba48b8671eb2, 602babaa84d627923713acaf5f7e9a4369e77473; azl3 kernel 6.6.56.1-5 on Azure Linux 3.0 6.6.57.1-1; azl3 kernel 6.6.57.1-1 on Azure Linux 3.0 6.6.57.1-1.
Low priority for now. Upgrade to Linux Linux 2fe399bb8efd0d325ab1138cf8e3ecf23a39e96d, 399927f0f875b93f3d5a0336d382ba48b8671eb2, 602babaa84d627923713acaf5f7e9a4369e77473; azl3 kernel 6.6.56.1-5 on Azure Linux 3.0 6.6.57.1-1; azl3 kernel 6.6.57.1-1 on Azure Linux 3.0 6.6.57.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 21, 2024
- Updated
- Oct 15, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- CWE-476
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 6.6.57
- linux linux kernel6.7 and later · before 6.11.4
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.7affected
- af224ca2df297440448b9d407d21b50982c6d532 and later · before 2fe399bb8efd0d325ab1138cf8e3ecf23a39e96daffected · git
- af224ca2df297440448b9d407d21b50982c6d532 and later · before 399927f0f875b93f3d5a0336d382ba48b8671eb2affected · git
- af224ca2df297440448b9d407d21b50982c6d532 and later · before d7b5876a6e74cdf8468a478be6b23f2f5464ac7aaffected · git
- af224ca2df297440448b9d407d21b50982c6d532 and later · before e418d91195d29d5f9c9685ff309b92b04b41dc40affected · git
- af224ca2df297440448b9d407d21b50982c6d532 and later · before 76ed24a34223bb2c6b6162e1d8389ec4e602a290affected · git
- af224ca2df297440448b9d407d21b50982c6d532 and later · before 602babaa84d627923713acaf5f7e9a4369e77473affected · git
- before 4.7not affected · semver
- 5.10.229 and later · up to and including 5.10.*not affected · semver
- 5.15.170 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.115-1 | 6.1.115-1 |
| Debian:13 | linux | before 6.11.4-1 | 6.11.4-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-50045Oct 21, 2024 · netfilter: br_netfilter: fix panic with metadata_dst skb22Monitor
- ← EarlierCVE-2024-50046Oct 21, 2024 · NFSv4: Prevent NULL-pointer dereference in nfs42_complete_copies()22Monitor
- Later →CVE-2024-50063Oct 21, 2024 · bpf: Prevent tail call between progs attached to different hooks31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2fe399bb8efd0d325ab1138cf8e3ecf23a39e96d | Vendor (CNA) |
| Linux Linux | 399927f0f875b93f3d5a0336d382ba48b8671eb2 | Vendor (CNA) |
| Linux Linux | 602babaa84d627923713acaf5f7e9a4369e77473 | Vendor (CNA) |
| Linux Linux | 76ed24a34223bb2c6b6162e1d8389ec4e602a290 | Vendor (CNA) |
| Linux Linux | d7b5876a6e74cdf8468a478be6b23f2f5464ac7a | Vendor (CNA) |
| Linux Linux | e418d91195d29d5f9c9685ff309b92b04b41dc40 | Vendor (CNA) |
| azl3 kernel 6.6.56.1-5 on Azure Linux 3.0 | 6.6.57.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kernel 6.6.57.1-1 on Azure Linux 3.0 | 6.6.57.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.176.3-1 on CBL Mariner 2.0 | 5.15.176.3-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.180.1-1 on CBL Mariner 2.0 | CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.180.1-1 on CBL-Mariner 2.0 | 5.15.176.3-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.115-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/399927f0f875b93f3d5a0336d382ba48b8671eb2
- git.kernel.org/stable/c/602babaa84d627923713acaf5f7e9a4369e77473
- git.kernel.org/stable/c/76ed24a34223bb2c6b6162e1d8389ec4e602a290
- git.kernel.org/stable/c/d7b5876a6e74cdf8468a478be6b23f2f5464ac7a
- git.kernel.org/stable/c/e418d91195d29d5f9c9685ff309b92b04b41dc40
- lists.debian.org/debian-lts-announce/2025/01/msg00001.html
- lists.debian.org/debian-lts-announce/2025/03/msg00002.html
- cert-portal.siemens.com/productcert/html/ssa-265688.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.