Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-39788scsi: ufs: exynos: Fix programming of HCI_UTRL_NEXUS_TYPE

Description

In the Linux kernel, the following vulnerability has been resolved: scsi: ufs: exynos: Fix programming of HCI_UTRL_NEXUS_TYPE On Google gs101, the number of UTP transfer request slots (nutrs) is 32, and in this case the driver ends up programming the UTRL_NEXUS_TYPE incorrectly as 0. This is because the left hand side of the shift is 1, which is of type int, i.e. 31 bits wide. Shifting by more than that width results in undefined behaviour. Fix this by switching to the BIT() macro, which applies correct type casting as required. This ensures the correct value is written to UTRL_NEXUS_TYPE (0xffffffff on gs101), and it also fixes a UBSAN shift warning: UBSAN: shift-out-of-bounds in drivers/ufs/host/ufs-exynos.c:1113:21 shift exponent 32 is too large for 32-bit type 'int' For consistency, apply the same change to the nutmrs / UTMRL_NEXUS_TYPE write.

Timeline

  1. ID reserved

    By Linux

  2. · 5 months later

    Published

  3. · 8 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-39788, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.18% · top 92% of all CVEs (13 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 55f4b1f73631a0817717fe6e98517de51b4c3527 – < 01510a9e8222f11cce064410f3c2fcf0756c0a08
    • affected 55f4b1f73631a0817717fe6e98517de51b4c3527 – < 098b2c8ee208c77126839047b9e6e1925bb35baa
    • affected 55f4b1f73631a0817717fe6e98517de51b4c3527 – < c1f025da8f370a015e412b55cbcc583f91de8316
    • affected 55f4b1f73631a0817717fe6e98517de51b4c3527 – < 6d53b2a134da77eb7fe65c5c7c7a3c193539a78a
    • affected 55f4b1f73631a0817717fe6e98517de51b4c3527 – < dc8fb963742f1a38d284946638f9358bdaa0ddee
    • affected 55f4b1f73631a0817717fe6e98517de51b4c3527 – < 5b9f1ef293428ea9c0871d96fcec2a87c4445832
    • affected 55f4b1f73631a0817717fe6e98517de51b4c3527 – < 01aad16c2257ab8ff33b152b972c9f2e1af47912
  • Linux · Linux

    • affected 5.9
    • unaffected < 5.9
    • unaffected 5.10.241 – ≤ 5.10.*
    • unaffected 5.15.190 – ≤ 5.15.*
    • unaffected 6.1.149 – ≤ 6.1.*
    • unaffected 6.6.103 – ≤ 6.6.*
    • unaffected 6.12.44 – ≤ 6.12.*
    • unaffected 6.16.4 – ≤ 6.16.*
    • unaffected 6.17 – ≤ *

References

References10

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-39788 badge
[![CVE-2025-39788](https://cveledger.app/badge/CVE-2025-39788.svg)](https://cveledger.app/cve/CVE-2025-39788)

Record last updated .