CVE-2026-53384: serial: 8250_dw: unregister 8250 port if clk_notifier_register() fails
Noroxi assessment
Priority: Monitor (action score 39/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.51% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Linux Linux 07ffe414a708ae60551401cec5d727ed156b8caf, 10fc708b4de7f86002d2d735a2dbf3b5b7f65692, 3d205fe80f2181f0109150ad1fa06ee5bc046935; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 07ffe414a708ae60551401cec5d727ed156b8caf, 10fc708b4de7f86002d2d735a2dbf3b5b7f65692, 3d205fe80f2181f0109150ad1fa06ee5bc046935; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.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: 8250_dw: unregister 8250 port if clk_notifier_register() fails dw8250_probe() registers the 8250 port via serial8250_register_8250_port() and then, if the device has a clock, registers a clock notifier. If clk_notifier_register() fails, probe returns the error but leaves the 8250 port registered. The matching serial8250_unregister_port() lives in dw8250_remove(), which is not called when probe fails, so the port slot stays occupied until the device is rebound or the system is rebooted. The devm-allocated driver data is freed while the port still references it (via the saved private_data and serial_in/serial_out callbacks), so any access to that port slot before a rebind is a use-after-free hazard. Unregister the port on the clk_notifier_register() error path.
- Published
- Jul 19, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.5% · 43th percentile
- CWE
- CWE-416
Report tools
Action score
39
Monitor
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 9.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 kernel5.19 and later · before 6.1.177
- linux linux kernel6.2 and later · before 6.6.144
- linux linux kernel6.7 and later · before 6.12.95
- linux linux kernel6.13 and later · before 6.18.38
- linux linux kernel6.19 and later · before 7.0.14
- linux linux kernel7.1 and later · before 7.1.2
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
- 5.19affected
- 57f83e5dd6a33c4696699954784f8fee789b1d0c and later · before ccdf4510a3873b14e5e348cdb038717996f09fdaaffected · git
- 57f83e5dd6a33c4696699954784f8fee789b1d0c and later · before 511d2b92f8d20de04acafab676150d26fb5c67f4affected · git
- 57f83e5dd6a33c4696699954784f8fee789b1d0c and later · before 07ffe414a708ae60551401cec5d727ed156b8cafaffected · git
- 57f83e5dd6a33c4696699954784f8fee789b1d0c and later · before 3d205fe80f2181f0109150ad1fa06ee5bc046935affected · git
- 57f83e5dd6a33c4696699954784f8fee789b1d0c and later · before d72650a4f334581b23a1892b888a4cb1be142f76affected · git
- 57f83e5dd6a33c4696699954784f8fee789b1d0c and later · before 778b9dda4b24005a27bcd9c35c110bf8d7f259caaffected · git
- 57f83e5dd6a33c4696699954784f8fee789b1d0c and later · before 10fc708b4de7f86002d2d735a2dbf3b5b7f65692affected · git
- before 5.19not affected · semver
- 6.1.177 and later · up to and including 6.1.*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.177-1 | 6.1.177-1 |
| Debian:13 | linux | before 6.12.95-1 | 6.12.95-1 |
| Debian:14 | linux | before 7.0.14-1 | 7.0.14-1 |
| openSUSE:Leap 16.0 | dtb-aarch64 | before 6.12.0-160000.39.1 | 6.12.0-160000.39.1 |
| openSUSE:Leap 16.0 | kernel-64kb | before 6.12.0-160000.39.1 | 6.12.0-160000.39.1 |
| openSUSE:Leap 16.0 | kernel-azure | before 6.12.0-160000.39.1 | 6.12.0-160000.39.1 |
| openSUSE:Leap 16.0 | kernel-default | before 6.12.0-160000.39.1 | 6.12.0-160000.39.1 |
| openSUSE:Leap 16.0 | kernel-default-base | before 6.12.0-160000.39.1.160000.2.25 | 6.12.0-160000.39.1.160000.2.25 |
| openSUSE:Leap 16.0 | kernel-docs | before 6.12.0-160000.39.1 | 6.12.0-160000.39.1 |
| openSUSE:Leap 16.0 | kernel-kvmsmall | before 6.12.0-160000.39.1 | 6.12.0-160000.39.1 |
| openSUSE:Leap 16.0 | kernel-obs-build | before 6.12.0-160000.39.1 | 6.12.0-160000.39.1 |
| openSUSE:Leap 16.0 | kernel-obs-qa | before 6.12.0-160000.39.1 | 6.12.0-160000.39.1 |
| openSUSE:Leap 16.0 | kernel-rt | before 6.12.0-160000.39.1 | 6.12.0-160000.39.1 |
| openSUSE:Leap 16.0 | kernel-source | before 6.12.0-160000.39.1 | 6.12.0-160000.39.1 |
| openSUSE:Leap 16.0 | kernel-syms | before 6.12.0-160000.39.1 | 6.12.0-160000.39.1 |
| openSUSE:Leap 16.0 | kernel-zfcpdump | before 6.12.0-160000.39.1 | 6.12.0-160000.39.1 |
| openSUSE:Tumbleweed | kernel-source | before 7.1.4-1.1 | 7.1.4-1.1 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7_Update_22 | before 1-150700.15.3.1 | 1-150700.15.3.1 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7-RT_Update_21 | before 1-150700.1.3.1 | 1-150700.1.3.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP7 | kernel-64kb | before 6.4.0-150700.53.84.1 | 6.4.0-150700.53.84.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP7 | kernel-default | before 6.4.0-150700.53.84.1 | 6.4.0-150700.53.84.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP7 | kernel-default-base | before 6.4.0-150700.53.84.1.150700.17.47.1 | 6.4.0-150700.53.84.1.150700.17.47.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP7 | kernel-source | before 6.4.0-150700.53.84.1 | 6.4.0-150700.53.84.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP7 | kernel-zfcpdump | before 6.4.0-150700.53.84.1 | 6.4.0-150700.53.84.1 |
+23
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-2026-53377Jul 19, 2026 · drm/msm: always recover the gpu22Monitor
- ← EarlierCVE-2026-53381Jul 19, 2026 · virtiofs: fix UAF on submount umount31Monitor
- Later →CVE-2026-53388Jul 19, 2026 · fuse: re-lock request before replacing page cache folio31Monitor
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 | 07ffe414a708ae60551401cec5d727ed156b8caf | Vendor (CNA) |
| Linux Linux | 10fc708b4de7f86002d2d735a2dbf3b5b7f65692 | Vendor (CNA) |
| Linux Linux | 3d205fe80f2181f0109150ad1fa06ee5bc046935 | Vendor (CNA) |
| Linux Linux | 511d2b92f8d20de04acafab676150d26fb5c67f4 | Vendor (CNA) |
| Linux Linux | 778b9dda4b24005a27bcd9c35c110bf8d7f259ca | Vendor (CNA) |
| Linux Linux | ccdf4510a3873b14e5e348cdb038717996f09fda | Vendor (CNA) |
| Linux Linux | d72650a4f334581b23a1892b888a4cb1be142f76 | Vendor (CNA) |
| azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 | 6.6.150.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.177-1 · Debian:12 | Package registry (OSV) |
| opensuse:dtb-aarch64 | 6.12.0-160000.39.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-64kb | 6.12.0-160000.39.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-azure | 6.12.0-160000.39.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default | 6.12.0-160000.39.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default-base | 6.12.0-160000.39.1.160000.2.25 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-docs | 6.12.0-160000.39.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-kvmsmall | 6.12.0-160000.39.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-build | 6.12.0-160000.39.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-qa | 6.12.0-160000.39.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-rt | 6.12.0-160000.39.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-source | 7.1.4-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:kernel-syms | 6.12.0-160000.39.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| suse:kernel-64kb | 6.12.0-160000.39.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-64kb | 6.4.0-150700.53.84.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7 | Package registry (OSV) |
| suse:kernel-azure | 6.12.0-160000.39.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-default | 6.4.0-150700.53.84.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7 | Package registry (OSV) |
| suse:kernel-default | 6.4.0-159998.53.1 · SUSE:Linux Micro 6.1 | Package registry (OSV) |
| suse:kernel-default-base | 6.4.0-150700.53.84.1.150700.17.47.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7 | Package registry (OSV) |
| suse:kernel-default-base | 6.4.0-159998.53.1.159998.21.38 · SUSE:Linux Micro 6.1 | Package registry (OSV) |
| suse:kernel-docs | 6.12.0-160000.39.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-docs | 6.4.0-150700.53.84.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP7 | Package registry (OSV) |
+15
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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0576 · Jul 20, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);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
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/10fc708b4de7f86002d2d735a2dbf3b5b7f65692
- git.kernel.org/stable/c/3d205fe80f2181f0109150ad1fa06ee5bc046935
- git.kernel.org/stable/c/511d2b92f8d20de04acafab676150d26fb5c67f4
- git.kernel.org/stable/c/778b9dda4b24005a27bcd9c35c110bf8d7f259ca
- git.kernel.org/stable/c/ccdf4510a3873b14e5e348cdb038717996f09fda
- git.kernel.org/stable/c/d72650a4f334581b23a1892b888a4cb1be142f76
Vendor advisories and official records. Exploit/PoC links are deliberately left out.