Kernel panic via concurrent UARTLite probing
Published Jul 9, 2025 · Updated Aug 5, 2026
A probe-time race in the Linux kernel UARTLite driver allows local users on affected embedded systems to crash the kernel. During concurrent device probes, one thread can bypass uart_register_driver while another has allocated uart_state but has not finished driver initialization, so ulite_assign passes incomplete state to uart_add_one_port. Reachability requires two UARTLite instances to probe within the initialization window; the documented consequence is a null-pointer panic during kernel startup or device binding.
Summary
What happened
A probe-time race in the Linux kernel UARTLite driver allows local users on affected embedded systems to crash the kernel. During concurrent device probes, one thread can bypass uart_register_driver while another has allocated uart_state but has not finished driver initialization, so ulite_assign passes incomplete state to uart_add_one_port. Reachability requires two UARTLite instances to probe within the initialization window; the documented consequence is a null-pointer panic during kernel startup or device binding.
The record
- CVE
- CVE-2025-38262
- Published
- Jul 9, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 9, 2025CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=238b8721a554a33a451a3f13bdb5be8fe5cfc927 <5015eed450005bab6e5cb6810f7a62eab0434fc4
- Affected versionversion=238b8721a554a33a451a3f13bdb5be8fe5cfc927 <685d29f2c5057b32c7b1b46f2a7d303b926c8f72
- Affected versionversion=238b8721a554a33a451a3f13bdb5be8fe5cfc927 <6bd697b5fc39fd24e2aa418c7b7d14469f550a93
- Affected versionversion=238b8721a554a33a451a3f13bdb5be8fe5cfc927 <6db06aaea07bb7c8e33a425cf7b98bf29ee6056e
- Affected versionversion=238b8721a554a33a451a3f13bdb5be8fe5cfc927 <8e958d10dd0ce5ae674cce460db5c9ca3f25243b
- Affected versionversion=238b8721a554a33a451a3f13bdb5be8fe5cfc927 <9c905fdbba68a6d73d39a6b7de9b9f0d6c46df87
- Affected versionversion=238b8721a554a33a451a3f13bdb5be8fe5cfc927 <f5e4229d94792b40e750f30c92bcf7a3107c72ef
- Affected versionversion=2.6.20
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo