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-23307can: ems_usb: ems_usb_read_bulk_callback(): check the proper length of a message

Description

In the Linux kernel, the following vulnerability has been resolved: can: ems_usb: ems_usb_read_bulk_callback(): check the proper length of a message When looking at the data in a USB urb, the actual_length is the size of the buffer passed to the driver, not the transfer_buffer_length which is set by the driver as the max size of the buffer. When parsing the messages in ems_usb_read_bulk_callback() properly check the size both at the beginning of parsing the message to make sure it is big enough for the expected structure, and at the end of the message to make sure we don't overflow past the end of the buffer for the next message.

Timeline

  1. ID reserved

    By Linux

  2. · 2 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-2026-23307, 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.13% · top 97% of all CVEs (15 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: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 702171adeed3607ee9603ec30ce081411e36ae42 – < aed172a2e2330131f0977d2acd3ec8883f413ec1
    • affected 702171adeed3607ee9603ec30ce081411e36ae42 – < f10177e6c4575aedaea580ce67d792fab7a2235e
    • affected 702171adeed3607ee9603ec30ce081411e36ae42 – < c703bbf8e9b4947e111c88d2ed09236a6772a471
    • affected 702171adeed3607ee9603ec30ce081411e36ae42 – < 1818974e1b5ef200e27f144c8cb8a246420bb54d
    • affected 702171adeed3607ee9603ec30ce081411e36ae42 – < 18f75b9cbdc3703f15965425ab69dee509b07785
    • affected 702171adeed3607ee9603ec30ce081411e36ae42 – < 1cf469026d4a2308eaa91d04dca4a900d07a5c2e
    • affected 702171adeed3607ee9603ec30ce081411e36ae42 – < 2833e13e2b099546abf5d40a483b4eb04ddd1f7b
    • affected 702171adeed3607ee9603ec30ce081411e36ae42 – < 38a01c9700b0dcafe97dfa9dc7531bf4a245deff
  • Linux · Linux

    • affected 2.6.32
    • unaffected < 2.6.32
    • 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.77 – ≤ 6.12.*
    • unaffected 6.18.17 – ≤ 6.18.*
    • unaffected 6.19.7 – ≤ 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-23307 badge
[![CVE-2026-23307](https://cveledger.app/badge/CVE-2026-23307.svg)](https://cveledger.app/cve/CVE-2026-23307)

Record last updated .