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-31759usb: ulpi: fix double free in ulpi_register_interface() error path

Description

In the Linux kernel, the following vulnerability has been resolved: usb: ulpi: fix double free in ulpi_register_interface() error path When device_register() fails, ulpi_register() calls put_device() on ulpi->dev. The device release callback ulpi_dev_release() drops the OF node reference and frees ulpi, but the current error path in ulpi_register_interface() then calls kfree(ulpi) again, causing a double free. Let put_device() handle the cleanup through ulpi_dev_release() and avoid freeing ulpi again in ulpi_register_interface().

Timeline

  1. ID reserved

    By Linux

  2. · 53 days later

    Published

  3. · 6 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-2026-31759, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.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.13% · top 97% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
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 289fcff4bcdb1dcc0ce8788b7ea0f58a9e4a495f – < 2f70ba9dae13a190673cc3f9b4aad52179738f60
    • affected 289fcff4bcdb1dcc0ce8788b7ea0f58a9e4a495f – < ee248e6e941e4f2e634df2bd43e5f1ef810ab6df
    • affected 289fcff4bcdb1dcc0ce8788b7ea0f58a9e4a495f – < 272a9b26c336a295e4e209157fed809706c1b1f7
    • affected 289fcff4bcdb1dcc0ce8788b7ea0f58a9e4a495f – < aaeae6533d77e6ed4def85baec01e2815ebbef61
    • affected 289fcff4bcdb1dcc0ce8788b7ea0f58a9e4a495f – < 8763f8317bb389aded32a32b08f6751cfff657d2
    • affected 289fcff4bcdb1dcc0ce8788b7ea0f58a9e4a495f – < 38c28fe25611099230f0965c925499bfcf46a795
    • affected 289fcff4bcdb1dcc0ce8788b7ea0f58a9e4a495f – < a6e5461f076c2ef63159f18e5cdbd30b50f0bc15
    • affected 289fcff4bcdb1dcc0ce8788b7ea0f58a9e4a495f – < 01af542392b5d41fd659d487015a71f627accce3
  • Linux · Linux

    • affected 4.2
    • unaffected < 4.2
    • unaffected 5.10.253 – ≤ 5.10.*
    • unaffected 5.15.203 – ≤ 5.15.*
    • unaffected 6.1.168 – ≤ 6.1.*
    • unaffected 6.6.134 – ≤ 6.6.*
    • unaffected 6.12.81 – ≤ 6.12.*
    • unaffected 6.18.22 – ≤ 6.18.*
    • unaffected 6.19.12 – ≤ 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-31759 badge
[![CVE-2026-31759](https://cveledger.app/badge/CVE-2026-31759.svg)](https://cveledger.app/cve/CVE-2026-31759)

Record last updated .