In the Linux kernel, the following vulnerability has been resolved: net: usb: kalmia: bound RX frame length in kalmia_rx_fixup() kalmia_rx_fixup()… (CVE-2026-64351)
In the Linux kernel, the following vulnerability has been resolved: net: usb: kalmia: bound RX frame length in kalmia_rx_fixup() kalmia_rx_fixup() computes usb_packet_length = skb->len - (2 * KALMIA_HEADER_LENGTH) as a u16, guarded only by a pre-loop check that skb->len is at least KALMIA_HEADER_LENGTH, which is 6. A device can deliver a short bulk-IN frame with skb->len in the 6 to 11 range, or leave a short trailing remainder on a later loop iteration. Either case underflows usb_packet_length to about 65530. That bypasses the usb_packet_length < ether_packet_length truncation path. The device-supplied ether_packet_length, a le16 up to 65535 read from header_start[2], then drives a memcmp() and the following skb_trim() and skb_pull() past the end of the rx buffer. The rx buffer is hard_mtu * 10, which is 14000 bytes. That is an out of bounds read. Require both the start and end framing headers to be present before subtracting them, on every loop iteration.
AI Analysis
Technical Summary
The Linux kernel's kalmia USB network driver contained a vulnerability in the kalmia_rx_fixup() function where usb_packet_length was computed as skb->len minus twice the KALMIA_HEADER_LENGTH (6), but only a minimal pre-loop check ensured skb->len was at least 6. A malicious device could send short bulk-IN frames with skb->len between 6 and 11 or leave a trailing remainder, causing usb_packet_length to underflow to a large unsigned value (~65530). This bypassed the intended truncation logic comparing usb_packet_length and ether_packet_length, allowing the device-supplied ether_packet_length (up to 65535) to drive memcmp(), skb_trim(), and skb_pull() calls beyond the allocated rx buffer size (14000 bytes), resulting in an out-of-bounds read. The vulnerability was fixed by requiring both start and end framing headers to be present before subtracting them in every loop iteration.
Potential Impact
The vulnerability allows a malicious USB device to cause out-of-bounds memory reads in kernel space by exploiting improper length calculations in the kalmia_rx_fixup() function. This can lead to information disclosure or kernel memory corruption. There is no indication of known exploits in the wild. The impact is limited to systems using the affected kalmia USB network driver in the Linux kernel.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since this is a Linux kernel vulnerability, monitor official Linux kernel security advisories for patches addressing CVE-2026-64351. Until a patch is applied, avoid using untrusted USB devices that could exploit this vulnerability.
In the Linux kernel, the following vulnerability has been resolved: net: usb: kalmia: bound RX frame length in kalmia_rx_fixup() kalmia_rx_fixup()… (CVE-2026-64351)
Description
In the Linux kernel, the following vulnerability has been resolved: net: usb: kalmia: bound RX frame length in kalmia_rx_fixup() kalmia_rx_fixup() computes usb_packet_length = skb->len - (2 * KALMIA_HEADER_LENGTH) as a u16, guarded only by a pre-loop check that skb->len is at least KALMIA_HEADER_LENGTH, which is 6. A device can deliver a short bulk-IN frame with skb->len in the 6 to 11 range, or leave a short trailing remainder on a later loop iteration. Either case underflows usb_packet_length to about 65530. That bypasses the usb_packet_length < ether_packet_length truncation path. The device-supplied ether_packet_length, a le16 up to 65535 read from header_start[2], then drives a memcmp() and the following skb_trim() and skb_pull() past the end of the rx buffer. The rx buffer is hard_mtu * 10, which is 14000 bytes. That is an out of bounds read. Require both the start and end framing headers to be present before subtracting them, on every loop iteration.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's kalmia USB network driver contained a vulnerability in the kalmia_rx_fixup() function where usb_packet_length was computed as skb->len minus twice the KALMIA_HEADER_LENGTH (6), but only a minimal pre-loop check ensured skb->len was at least 6. A malicious device could send short bulk-IN frames with skb->len between 6 and 11 or leave a trailing remainder, causing usb_packet_length to underflow to a large unsigned value (~65530). This bypassed the intended truncation logic comparing usb_packet_length and ether_packet_length, allowing the device-supplied ether_packet_length (up to 65535) to drive memcmp(), skb_trim(), and skb_pull() calls beyond the allocated rx buffer size (14000 bytes), resulting in an out-of-bounds read. The vulnerability was fixed by requiring both start and end framing headers to be present before subtracting them in every loop iteration.
Potential Impact
The vulnerability allows a malicious USB device to cause out-of-bounds memory reads in kernel space by exploiting improper length calculations in the kalmia_rx_fixup() function. This can lead to information disclosure or kernel memory corruption. There is no indication of known exploits in the wild. The impact is limited to systems using the affected kalmia USB network driver in the Linux kernel.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since this is a Linux kernel vulnerability, monitor official Linux kernel security advisories for patches addressing CVE-2026-64351. Until a patch is applied, avoid using untrusted USB devices that could exploit this vulnerability.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-8qc4-xrrp-xx3v
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64351"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a65420c9c2644c7f8085385
Added to database: 07/25/2026, 23:09:00 UTC
Last enriched: 07/25/2026, 23:33:08 UTC
Last updated: 09/08/2026, 10:52:11 UTC
Views: 46
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.