[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"repo-stars":3,"vuln-DEBIAN-CVE-2024-26853":6},{"stargazers_count":4,"fetched_at":5},7,"2026-06-04T14:53:31.930Z",{"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-2024-26853","In the Linux kernel, the following vulnerability has been resolved:  igc: avoid returning frame twice in XDP_REDIRECT  When a frame can not be transmitted in XDP_REDIRECT (e.g. due to a full queue), it is necessary to free it by calling xdp_return_frame_rx_napi.  However, this is the responsibility of the caller of the ndo_xdp_xmit (see for example bq_xmit_all in kernel/bpf/devmap.c) and thus calling it inside igc_xdp_xmit (which is the ndo_xdp_xmit of the igc driver) as well will lead to memory corruption.  In fact, bq_xmit_all expects that it can return all frames after the last successfully transmitted one. Therefore, break for the first not transmitted frame, but do not call xdp_return_frame_rx_napi in igc_xdp_xmit. This is equally implemented in other Intel drivers such as the igb.  There are two alternatives to this that were rejected: 1. Return num_frames as all the frames would have been    transmitted and release them inside igc_xdp_xmit.    While it might work technically, it is not what    the return value is meant to represent (i.e. the    number of SUCCESSFULLY transmitted packets). 2. Rework kernel/bpf/devmap.c and all drivers to    support non-consecutively dropped packets.    Besides being complex, it likely has a negative    performance impact without a significant gain    since it is anyway unlikely that the next frame    can be transmitted if the previous one was dropped.  The memory corruption can be reproduced with the following script which leads to a kernel panic after a few seconds.  It basically generates more traffic than a i225 NIC can transmit and pushes it via XDP_REDIRECT from a virtual interface to the physical interface where frames get dropped.     #!/bin/bash    INTERFACE=enp4s0    INTERFACE_IDX=`cat /sys/class/net/$INTERFACE/ifindex`     sudo ip link add dev veth1 type veth peer name veth2    sudo ip link set up $INTERFACE    sudo ip link set up veth1    sudo ip link set up veth2     cat \u003C\u003C EOF > redirect.bpf.c     SEC(\"prog\")    int redirect(struct xdp_md *ctx)    {        return bpf_redirect($INTERFACE_IDX, 0);    }     char _license[] SEC(\"license\") = \"GPL\";    EOF    clang -O2 -g -Wall -target bpf -c redirect.bpf.c -o redirect.bpf.o    sudo ip link set veth2 xdp obj redirect.bpf.o     cat \u003C\u003C EOF > pass.bpf.c     SEC(\"prog\")    int pass(struct xdp_md *ctx)    {        return XDP_PASS;    }     char _license[] SEC(\"license\") = \"GPL\";    EOF    clang -O2 -g -Wall -target bpf -c pass.bpf.c -o pass.bpf.o    sudo ip link set $INTERFACE xdp obj pass.bpf.o     cat \u003C\u003C EOF > trafgen.cfg     {      /* Ethernet Header */      0xe8, 0x6a, 0x64, 0x41, 0xbf, 0x46,      0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF,      const16(ETH_P_IP),       /* IPv4 Header */      0b01000101, 0,   # IPv4 version, IHL, TOS      const16(1028),   # IPv4 total length (UDP length + 20 bytes (IP header))      const16(2),      # IPv4 ident      0b01000000, 0,   # IPv4 flags, fragmentation off      64,              # IPv4 TTL      17,              # Protocol UDP      csumip(14, 33),  # IPv4 checksum       /* UDP Header */      10,  0, 1, 1,    # IP Src - adapt as needed      10,  0, 1, 2,    # IP Dest - adapt as needed      const16(6666),   # UDP Src Port      const16(6666),   # UDP Dest Port      const16(1008),   # UDP length (UDP header 8 bytes + payload length)      csumudp(14, 34), # UDP checksum       /* Payload */      fill('W', 1000),    }    EOF     sudo trafgen -i trafgen.cfg -b3000MB -o veth1 --cpp",null,[],[],[],[14],{"_key":15},"CVE-2024-26853",[],[],[],"2024-04-17T11:15:08.583Z","2026-04-28T20:27:43.263770Z",{"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-2024-26853",[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},5.5,"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",6,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,55],{"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_1_82_1",true,"ecosystem","6.1.82-1","excluding",{"version":53,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":54,"version_end_type":51,"fixed_in":9},"lt6_7_12_1","6.7.12-1",{"version":53,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":54,"version_end_type":51,"fixed_in":9}]