Data exposure or service interruption via chip-select indexing
Published Jun 18, 2025 · Updated May 11, 2026
Out-of-bounds register access in the Linux spi-rockchip driver allows local users to read protected data or interrupt the system. The rockchip_spi_config() function uses a GPIO-backed chip-select number as a native register-field bit index when SPI_CS_HIGH is set, so a high GPIO number selects bits outside the native chip-select field. Reachability requires Rockchip SPI hardware configured with an active-high GPIO chip select; published assessments disagree on whether register corruption also permits integrity impact.
Summary
What happened
Out-of-bounds register access in the Linux spi-rockchip driver allows local users to read protected data or interrupt the system. The rockchip_spi_config() function uses a GPIO-backed chip-select number as a native register-field bit index when SPI_CS_HIGH is set, so a high GPIO number selects bits outside the native chip-select field. Reachability requires Rockchip SPI hardware configured with an active-high GPIO chip select; published assessments disagree on whether register corruption also permits integrity impact.
The record
- CVE
- CVE-2025-38081
- Published
- Jun 18, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 18, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 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=5.14
- Affected versionversion=736b81e075172f1e6cd7a8bc1a1374a2dee9e4dc <254e04ec799c1ff8c1e2bd08a57c6a849895d6ff
- Affected versionversion=736b81e075172f1e6cd7a8bc1a1374a2dee9e4dc <4a120221661fcecb253448d7b041a52d47f1d91f
- Affected versionversion=736b81e075172f1e6cd7a8bc1a1374a2dee9e4dc <7a874e8b54ea21094f7fd2d428b164394c6cb316
- Affected versionversion=736b81e075172f1e6cd7a8bc1a1374a2dee9e4dc <ace57bd1fb49d193edec5f6a1f255f48dd5fca90
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
No sourced classifications are available.
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