[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"repo-stars":3,"vuln-DEBIAN-CVE-2025-38224":6},{"stargazers_count":4,"fetched_at":5},7,"2026-07-31T03:17:55.401Z",{"id":7,"descriptions":8,"cisa":9,"weaknesses":10,"exploits":11,"aliases":12,"duplicate_of":9,"upstream":13,"downstream":16,"duplicates":17,"related":18,"reserved_at":9,"published_at":19,"modified_at":20,"state":9,"summary":21,"references_raw":23,"kevs":30,"epss":9,"epss_history":31,"metrics":32,"affected":39},"DEBIAN-CVE-2025-38224","In the Linux kernel, the following vulnerability has been resolved:  can: kvaser_pciefd: refine error prone echo_skb_max handling logic  echo_skb_max should define the supported upper limit of echo_skb[] allocated inside the netdevice's priv. The corresponding size value provided by this driver to alloc_candev() is KVASER_PCIEFD_CAN_TX_MAX_COUNT which is 17.  But later echo_skb_max is rounded up to the nearest power of two (for the max case, that would be 32) and the tx/ack indices calculated further during tx/rx may exceed the upper array boundary. Kasan reported this for the ack case inside kvaser_pciefd_handle_ack_packet(), though the xmit function has actually caught the same thing earlier.   BUG: KASAN: slab-out-of-bounds in kvaser_pciefd_handle_ack_packet+0x2d7/0x92a drivers/net/can/kvaser_pciefd.c:1528  Read of size 8 at addr ffff888105e4f078 by task swapper/4/0   CPU: 4 UID: 0 PID: 0 Comm: swapper/4 Not tainted 6.15.0 #12 PREEMPT(voluntary)  Call Trace:   \u003CIRQ>  dump_stack_lvl lib/dump_stack.c:122  print_report mm/kasan/report.c:521  kasan_report mm/kasan/report.c:634  kvaser_pciefd_handle_ack_packet drivers/net/can/kvaser_pciefd.c:1528  kvaser_pciefd_read_packet drivers/net/can/kvaser_pciefd.c:1605  kvaser_pciefd_read_buffer drivers/net/can/kvaser_pciefd.c:1656  kvaser_pciefd_receive_irq drivers/net/can/kvaser_pciefd.c:1684  kvaser_pciefd_irq_handler drivers/net/can/kvaser_pciefd.c:1733  __handle_irq_event_percpu kernel/irq/handle.c:158  handle_irq_event kernel/irq/handle.c:210  handle_edge_irq kernel/irq/chip.c:833  __common_interrupt arch/x86/kernel/irq.c:296  common_interrupt arch/x86/kernel/irq.c:286   \u003C/IRQ>  Tx max count definitely matters for kvaser_pciefd_tx_avail(), but for seq numbers' generation that's not the case - we're free to calculate them as would be more convenient, not taking tx max count into account. The only downside is that the size of echo_skb[] should correspond to the max seq number (not tx max count), so in some situations a bit more memory would be consumed than could be.  Thus make the size of the underlying echo_skb[] sufficient for the rounded max tx value.  Found by Linux Verification Center (linuxtesting.org) with Syzkaller.",null,[],[],[],[14],{"_key":15},"CVE-2025-38224",[],[],[],"2025-07-04T14:15:31.110Z","2026-06-15T19:05:44.959775044Z",{"cisa_kev":22,"cisa_ransomware":22,"cisa_vendor":9,"epss_severity":9,"epss_score":9,"severity":9,"severity_score":9,"severity_version":9,"severity_source":9,"severity_vector":9,"severity_status":9},false,[24],{"url":25,"sources":26,"tags":28},"https://security-tracker.debian.org/tracker/CVE-2025-38224",[27],"osv_debian",[29],"Advisory",[],[],[33],{"source":27,"cvss_v2_0":9,"cvss_v3_0":9,"cvss_v3_1":34,"cvss_v4_0":9},{"baseScore":35,"baseSeverity":9,"vectorString":36,"impactScore":37,"exploitabilityScore":38},7.1,"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H",8.7,4.6,[40],{"ecosystem":41,"name":42,"vendor":43,"product":42,"cpe_part":9,"purl_type":44,"purl_namespace":43,"purl_name":42,"source":9,"versions":45},"Debian","linux","debian","deb",[46,52],{"version":47,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":50,"version_end_type":51,"fixed_in":9},"lt6_12_35_1",true,"ecosystem","6.12.35-1","excluding",{"version":47,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":50,"version_end_type":51,"fixed_in":9}]