CVE-2026-64528: tty: serial: samsung: Remove redundant port lock acquisition in rx helpers
Noroxi assessment
Priority: Monitor (action score 0/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.16% (FIRST EPSS).
- Fixed version: Linux Linux 10014eb7eee351f7b587f8ac85830f0c9343cb9a, 14143ec10d69f42806b5d7b046f0fd1b835831ae, 9c92b42207978559e32903c3098aaf5c5b5788b2.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 10014eb7eee351f7b587f8ac85830f0c9343cb9a, 14143ec10d69f42806b5d7b046f0fd1b835831ae, 9c92b42207978559e32903c3098aaf5c5b5788b2 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: tty: serial: samsung: Remove redundant port lock acquisition in rx helpers Sashiko identified a deadlock when the console flow is engaged [1]. When console flow control is enabled (UPF_CONS_FLOW), s3c24xx_serial_stop_tx() calls s3c24xx_serial_rx_enable() and s3c24xx_serial_start_tx() calls s3c24xx_serial_rx_disable(). The serial core framework invokes the .stop_tx() and .start_tx() callbacks with the port->lock spinlock already held. Furthermore, all internal driver paths that invoke stop_tx (such as the DMA TX completion handler s3c24xx_serial_tx_dma_complete() or the PIO TX IRQ handler s3c24xx_serial_tx_irq()) also acquire port->lock prior to calling it. (Note that s3c24xx_serial_start_tx() is only invoked by the serial core). However, s3c24xx_serial_rx_enable() and s3c24xx_serial_rx_disable() unconditionally attempt to acquire port->lock again using uart_port_lock_irqsave(). Since spinlocks are not recursive, this causes a deadlock on the same CPU when console flow control is engaged. Remove the redundant lock acquisition from both rx helper functions.
- Published
- Jul 25, 2026
- Updated
- Nov 3, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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.
—
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
- 2.6.27affected
- b497549a035c2a81b71c7a27f2b00c8a16c09423 and later · before ee9eb72be95490602c493db050c73d925c3a4d74affected · git
- b497549a035c2a81b71c7a27f2b00c8a16c09423 and later · before 10014eb7eee351f7b587f8ac85830f0c9343cb9aaffected · git
- b497549a035c2a81b71c7a27f2b00c8a16c09423 and later · before f4c3e63fa8639aedf96fb200d9939945a9eed51eaffected · git
- b497549a035c2a81b71c7a27f2b00c8a16c09423 and later · before a9c22e0f93ba18322a6623ecdda2f0cd858ca350affected · git
- b497549a035c2a81b71c7a27f2b00c8a16c09423 and later · before 14143ec10d69f42806b5d7b046f0fd1b835831aeaffected · git
- b497549a035c2a81b71c7a27f2b00c8a16c09423 and later · before 9fd48937046efc9abb89379d63ee9cc5c661d711affected · git
- b497549a035c2a81b71c7a27f2b00c8a16c09423 and later · before 9c92b42207978559e32903c3098aaf5c5b5788b2affected · git
- b497549a035c2a81b71c7a27f2b00c8a16c09423 and later · before a3bb136bff5e6a5e48cdd813246c9c4686feaaa9affected · git
- before 2.6.27not 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.176-1 | 6.1.176-1 |
| Debian:13 | linux | before 6.12.94-1 | 6.12.94-1 |
| Debian:14 | linux | before 7.0.12-1 | 7.0.12-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-64526Jul 25, 2026 · ethtool: tsconfig: fix missing ethnl_ops_complete()0Monitor
- ← EarlierCVE-2026-64527Jul 25, 2026 · drm/hyperv: validate VMBus packet size in receive callback0Monitor
- Later →CVE-2026-64529Jul 25, 2026 · crypto: qat - remove unused character device and IOCTLs31Monitor
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 | 10014eb7eee351f7b587f8ac85830f0c9343cb9a | Vendor (CNA) |
| Linux Linux | 14143ec10d69f42806b5d7b046f0fd1b835831ae | Vendor (CNA) |
| Linux Linux | 9c92b42207978559e32903c3098aaf5c5b5788b2 | Vendor (CNA) |
| Linux Linux | 9fd48937046efc9abb89379d63ee9cc5c661d711 | Vendor (CNA) |
| Linux Linux | a3bb136bff5e6a5e48cdd813246c9c4686feaaa9 | Vendor (CNA) |
| Linux Linux | a9c22e0f93ba18322a6623ecdda2f0cd858ca350 | Vendor (CNA) |
| Linux Linux | ee9eb72be95490602c493db050c73d925c3a4d74 | Vendor (CNA) |
| Linux Linux | f4c3e63fa8639aedf96fb200d9939945a9eed51e | Vendor (CNA) |
| debian:linux | 6.1.176-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.
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-0636 · Jul 27, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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 (7 more)Show less
- git.kernel.org/stable/c/14143ec10d69f42806b5d7b046f0fd1b835831ae
- git.kernel.org/stable/c/9c92b42207978559e32903c3098aaf5c5b5788b2
- git.kernel.org/stable/c/9fd48937046efc9abb89379d63ee9cc5c661d711
- git.kernel.org/stable/c/a3bb136bff5e6a5e48cdd813246c9c4686feaaa9
- git.kernel.org/stable/c/a9c22e0f93ba18322a6623ecdda2f0cd858ca350
- git.kernel.org/stable/c/ee9eb72be95490602c493db050c73d925c3a4d74
- git.kernel.org/stable/c/f4c3e63fa8639aedf96fb200d9939945a9eed51e
Vendor advisories and official records. Exploit/PoC links are deliberately left out.