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-38507HID: nintendo: avoid bluetooth suspend/resume stalls

Description

In the Linux kernel, the following vulnerability has been resolved: HID: nintendo: avoid bluetooth suspend/resume stalls Ensure we don't stall or panic the kernel when using bluetooth-connected controllers. This was reported as an issue on android devices using kernel 6.6 due to the resume hook which had been added for usb joycons. First, set a new state value to JOYCON_CTLR_STATE_SUSPENDED in a newly-added nintendo_hid_suspend. This makes sure we will not stall out the kernel waiting for input reports during led classdev suspend. The stalls could happen if connectivity is unreliable or lost to the controller prior to suspend. Second, since we lose connectivity during suspend, do not try joycon_init() for bluetooth controllers in the nintendo_hid_resume path. Tested via multiple suspend/resume flows when using the controller both in USB and bluetooth modes.

Timeline

  1. ID reserved

    By Linux

  2. · 4 months later

    Published

  3. · 15 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-38507, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.23% · top 86% of all CVEs (18 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 2af16c1f846bd60240745bbd3afa13d5f040c61a – < 167c610b45b4c23a954aac70df9760a4bf358b20
    • affected 2af16c1f846bd60240745bbd3afa13d5f040c61a – < d3c8519f85b786dcae2498b3496f32e3925e4601
    • affected 2af16c1f846bd60240745bbd3afa13d5f040c61a – < 7b4a026313529a487821ef6ab494a61f12c1db08
    • affected 2af16c1f846bd60240745bbd3afa13d5f040c61a – < 72cb7eef06a5cde42b324dea85fa11fd5bb6a08a
    • affected 2af16c1f846bd60240745bbd3afa13d5f040c61a – < 4a0381080397e77792a5168069f174d3e56175ff
  • Linux · Linux

    • affected 5.16
    • unaffected < 5.16
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.39 – ≤ 6.12.*
    • unaffected 6.15.7 – ≤ 6.15.*
    • unaffected 6.16 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .