Strix
26.1K

CVE-2026-23058

UnknownEPSS 0.17%

Last modified

CVE-2026-23058 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: can: ems_usb: ems_usb_read_bulk_callback(): fix URB memory leak Fix similar memory leak as in commit 7352e1d5932a ("can: gs_usb: gs_usb_receive_bulk_callback(): fix URB memory leak"). In ems_usb_open(), the URBs for USB-in transfers are allocated, added to the dev->rx_submitted anchor and submitted. In the complete callback ems_usb_read_bulk_callback(), the URBs are processed and resubmitted. EPSS estimates a 0.17% chance of exploitation in the next 30 days.

Description

In the Linux kernel, the following vulnerability has been resolved: can: ems_usb: ems_usb_read_bulk_callback(): fix URB memory leak Fix similar memory leak as in commit 7352e1d5932a ("can: gs_usb: gs_usb_receive_bulk_callback(): fix URB memory leak"). In ems_usb_open(), the URBs for USB-in transfers are allocated, added to the dev->rx_submitted anchor and submitted. In the complete callback ems_usb_read_bulk_callback(), the URBs are processed and resubmitted. In ems_usb_close() the URBs are freed by calling usb_kill_anchored_urbs(&dev->rx_submitted). However, this does not take into account that the USB framework unanchors the URB before the complete function is called. This means that once an in-URB has been completed, it is no longer anchored and is ultimately not released in ems_usb_close(). Fix the memory leak by anchoring the URB in the ems_usb_read_bulk_callback() to the dev->rx_submitted anchor.

Metrics

EPSS Probability
0.17%

7.0th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 702171adeed3607ee9603ec30ce081411e36ae42, < e2c71030dc464d437110bcfb367c493fd402bddb; >= 702171adeed3607ee9603ec30ce081411e36ae42, < f48eabd15194b216030b32445f44230df95f5fe0; >= 702171adeed3607ee9603ec30ce081411e36ae42, < 61e6d3674c3d1da1475dc207b3e75c55d678d18e; >= 702171adeed3607ee9603ec30ce081411e36ae42, < e9410fdd4d5f7eaa6526d8c80e83029d7c86a8e8; >= 702171adeed3607ee9603ec30ce081411e36ae42, < 46a191ff7eeec33a2ccb2a1bfea34e18fbc5dc1a; >= 702171adeed3607ee9603ec30ce081411e36ae42, < 68c62b3e53901846b5f68c5a8bade72a5d9c0b87; >= 702171adeed3607ee9603ec30ce081411e36ae42, < 0ce73a0eb5a27070957b67fd74059b6da89cc516
LinuxLinux2.6.32

References

Timeline

Published
Last Modified
Status
Deferred

Frequently Asked Questions

What is CVE-2026-23058?
In the Linux kernel, the following vulnerability has been resolved: can: ems_usb: ems_usb_read_bulk_callback(): fix URB memory leak Fix similar memory leak as in commit 7352e1d5932a ("can: gs_usb: gs_usb_receive_bulk_callback(): fix URB memory leak"). In ems_usb_open(), the URBs for USB-in transfers are allocated, added to the dev->rx_submitted anchor and submitted. In the complete callback ems_usb_read_bulk_callback(), the URBs are processed and resubmitted. In ems_usb_close() the URBs are freed by calling usb_kill_anchored_urbs(&dev->rx_submitted). However, this does not take into account that the USB framework unanchors the URB before the complete function is called. This means that once an in-URB has been completed, it is no longer anchored and is ultimately not released in ems_usb_close(). Fix the memory leak by anchoring the URB in the ems_usb_read_bulk_callback() to the dev->rx_submitted anchor.
How severe is CVE-2026-23058?
Severity scoring for CVE-2026-23058 is pending analysis. The EPSS model estimates a 0.17% probability of exploitation in the next 30 days.
How do I fix CVE-2026-23058?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-23058?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST