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-2026-43381nouveau/dpcd: return EBUSY for aux xfer if the device is asleep

Description

In the Linux kernel, the following vulnerability has been resolved: nouveau/dpcd: return EBUSY for aux xfer if the device is asleep If we have runtime suspended, and userspace wants to use /dev/drm_dp_* then just tell it the device is busy instead of crashing in the GSP code. WARNING: CPU: 2 PID: 565741 at drivers/gpu/drm/nouveau/nvkm/subdev/gsp/rm/r535/rpc.c:164 r535_gsp_msgq_wait+0x9a/0xb0 [nouveau] CPU: 2 UID: 0 PID: 565741 Comm: fwupd Not tainted 6.18.10-200.fc43.x86_64 #1 PREEMPT(lazy) Hardware name: LENOVO 20QTS0PQ00/20QTS0PQ00, BIOS N2OET65W (1.52 ) 08/05/2024 RIP: 0010:r535_gsp_msgq_wait+0x9a/0xb0 [nouveau] This is a simple fix to get backported. We should probably engineer a proper power domain solution to wake up devices and keep them awake while fw updates are happening.

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    Published

  3. · 3 days 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-2026-43381, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.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.12% · top 98% of all CVEs (15 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 8894f4919bc43f821775db2cfff4b917871b2102 – < 178df7c91e6c202579284df9f79d1592a514cdcf
    • affected 8894f4919bc43f821775db2cfff4b917871b2102 – < 4df518aa196085909fd7e32518ecd27fba60ed69
    • affected 8894f4919bc43f821775db2cfff4b917871b2102 – < cd24cab2023aa46b595bc6b9cc39d8973d9d0a8c
    • affected 8894f4919bc43f821775db2cfff4b917871b2102 – < fad178ae894930520519ead3c8e0150641466360
    • affected 8894f4919bc43f821775db2cfff4b917871b2102 – < 6bdd2d70c338d52c387d3b3aadc596784ae81b01
    • affected 8894f4919bc43f821775db2cfff4b917871b2102 – < ad8fa5bff53f5d1f8394f996850da8ce070eaee3
    • affected 8894f4919bc43f821775db2cfff4b917871b2102 – < 24639553a016578222ac597db924dfb6fa5ec8b5
    • affected 8894f4919bc43f821775db2cfff4b917871b2102 – < 8f3c6f08ababad2e3bdd239728cf66a9949446b4
  • Linux · Linux

    • affected 3.16
    • unaffected < 3.16
    • unaffected 5.10.253 – ≤ 5.10.*
    • unaffected 5.15.203 – ≤ 5.15.*
    • unaffected 6.1.167 – ≤ 6.1.*
    • unaffected 6.6.130 – ≤ 6.6.*
    • unaffected 6.12.78 – ≤ 6.12.*
    • unaffected 6.18.19 – ≤ 6.18.*
    • unaffected 6.19.9 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .