CVE-2026-23061None▾ SunlitIn the Linux kernel, the following vulnerability has been resolved: can: kvaser_usb: kvaser_usb_read_bulk_callback(): fix URB memory leak Fix similar memory leak as in commit 7352e1d5932a ("can: gs_usb: gs_usb_receive_bulk_callback(): …
▾ Sunlit zone — Low / medium · no exploitation signal
impact 2.8 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake.
Exploit-prediction probability, daily snapshots since Oct 19.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.1%
0.1% → 0.2%
In the Linux kernel, the following vulnerability has been resolved:
can: kvaser_usb: kvaser_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 kvaser_usb_set_{,data_}bittiming() -> kvaser_usb_setup_rx_urbs(), the URBs for USB-in transfers are allocated, added to the dev->rx_submitted anchor and submitted. In the complete callback kvaser_usb_read_bulk_callback(), the URBs are processed and resubmitted. In kvaser_usb_remove_interfaces() 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 usb_kill_anchored_urbs().
Fix the memory leak by anchoring the URB in the kvaser_usb_read_bulk_callback() to the dev->rx_submitted anchor.
Linux >= 080f40a6fa28dab299da7a652e444b1e2d9231e7 < d9d824582f2ec76459ffab449e9b05c7bc49645cLinux >= 080f40a6fa28dab299da7a652e444b1e2d9231e7 < 40a3334ffda479c63e416e61ff086485e24401f7Linux >= 080f40a6fa28dab299da7a652e444b1e2d9231e7 < c1b39fa24c140bc616f51fef4175c1743e2bb132Linux >= 080f40a6fa28dab299da7a652e444b1e2d9231e7 < 7c308f7530bffafa994e0aa8dc651a312f4b9ff4Linux >= 080f40a6fa28dab299da7a652e444b1e2d9231e7 < 94a7fc42e21c7d9d1c49778cd1db52de5df52a01Linux >= 080f40a6fa28dab299da7a652e444b1e2d9231e7 < 3b1a593eab941c3f32417896cc7df564191f2482Linux >= 080f40a6fa28dab299da7a652e444b1e2d9231e7 < 248e8e1a125fa875158df521b30f2cc7e27eeeaaLinux 3.8Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99118Nonedrm/i915/dmc: Harden DMC firmware payload parsing
CVE-2026-99117Nonenet: bridge: mcast: don't truncate the port group walk on teardown
CVE-2026-99121Noneipv4: avoid divide by zero in fib_rebalance
CVE-2026-99120NoneKVM: x86/mmu: Cope with the SS bit being set in #NPF exit codes
CVE-2026-99119Nonedrm/amdgpu/userq: actually validate userq BOs
CVE-2026-99123Nonevsock/virtio: validate packet source for connected sockets