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-90329HID: synchronize input before cleaning up a failed probe

Description

In the Linux kernel, the following vulnerability has been resolved: HID: synchronize input before cleaning up a failed probe hid_device_io_start() allows reports to run concurrently with probe. If the probe subsequently fails, __hid_device_probe() releases driver resources and clears hdev->driver without first excluding those report callbacks. For example, a report may enter hidraw_report_event() while the failure path frees the associated hidraw object, leading to a use-after-free when the report takes the object's list lock. Stop input before performing failed-probe cleanup. This reacquires driver_input_lock and waits for any report callback already in progress.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 32 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-90329, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.8CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High8.8CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.34% · top 72% 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 8.8.

Affected products

  • Linux · Linux

    • affected c849a6143bec520aff2a6646518b0d041402428b – < 3ffb088a2ed34ca982cfc2c81d107ce370aa45f1
    • affected c849a6143bec520aff2a6646518b0d041402428b – < 2c35cdeb13a0c52429501e66f368fa59cad235f6
    • affected c849a6143bec520aff2a6646518b0d041402428b – < 98201b46f7e33fe11af6f024fecb40fb56634225
    • affected c849a6143bec520aff2a6646518b0d041402428b – < 9a3da56aae28e1ad3a3e591f72a537742053ecd2
    • affected c849a6143bec520aff2a6646518b0d041402428b – < edd490b8ad85c052eaf10dcc9f390ea54f1e1b39
    • affected c849a6143bec520aff2a6646518b0d041402428b – < 01eeb601a1626e683fb7b77c63f442b06fb87093
    • affected c849a6143bec520aff2a6646518b0d041402428b – < b85d1000eb8842768970f2fd0a8fd362472d02d5
    • affected c849a6143bec520aff2a6646518b0d041402428b – < 207853d46f7ef2e28042344a1468da8754c3ddbf
  • Linux · Linux

    • affected 3.10
    • unaffected < 3.10
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .