[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"repo-stars":3,"vuln-DEBIAN-CVE-2024-45001":6},{"stargazers_count":4,"fetched_at":5},7,"2026-06-04T08:53:30.047Z",{"id":7,"descriptions":8,"cisa":9,"weaknesses":10,"exploits":11,"aliases":12,"duplicate_of":9,"upstream":13,"downstream":16,"duplicates":19,"related":20,"reserved_at":9,"published_at":21,"modified_at":22,"state":9,"summary":23,"references_raw":25,"kevs":32,"epss":9,"epss_history":33,"metrics":34,"affected":41},"DEBIAN-CVE-2024-45001","In the Linux kernel, the following vulnerability has been resolved:  net: mana: Fix RX buf alloc_size alignment and atomic op panic  The MANA driver's RX buffer alloc_size is passed into napi_build_skb() to create SKB. skb_shinfo(skb) is located at the end of skb, and its alignment is affected by the alloc_size passed into napi_build_skb(). The size needs to be aligned properly for better performance and atomic operations. Otherwise, on ARM64 CPU, for certain MTU settings like 4000, atomic operations may panic on the skb_shinfo(skb)->dataref due to alignment fault.  To fix this bug, add proper alignment to the alloc_size calculation.  Sample panic info: [  253.298819] Unable to handle kernel paging request at virtual address ffff000129ba5cce [  253.300900] Mem abort info: [  253.301760]   ESR = 0x0000000096000021 [  253.302825]   EC = 0x25: DABT (current EL), IL = 32 bits [  253.304268]   SET = 0, FnV = 0 [  253.305172]   EA = 0, S1PTW = 0 [  253.306103]   FSC = 0x21: alignment fault Call trace:  __skb_clone+0xfc/0x198  skb_clone+0x78/0xe0  raw6_local_deliver+0xfc/0x228  ip6_protocol_deliver_rcu+0x80/0x500  ip6_input_finish+0x48/0x80  ip6_input+0x48/0xc0  ip6_sublist_rcv_finish+0x50/0x78  ip6_sublist_rcv+0x1cc/0x2b8  ipv6_list_rcv+0x100/0x150  __netif_receive_skb_list_core+0x180/0x220  netif_receive_skb_list_internal+0x198/0x2a8  __napi_poll+0x138/0x250  net_rx_action+0x148/0x330  handle_softirqs+0x12c/0x3a0",null,[],[],[],[14],{"_key":15},"CVE-2024-45001",[17],{"_key":18},"DLA-4102-1",[],[],"2024-09-04T20:15:08.710Z","2026-04-28T20:28:31.632298Z",{"cisa_kev":24,"cisa_ransomware":24,"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,[26],{"url":27,"sources":28,"tags":30},"https://security-tracker.debian.org/tracker/CVE-2024-45001",[29],"osv_debian",[31],"Advisory",[],[],[35],{"source":29,"cvss_v2_0":9,"cvss_v3_0":9,"cvss_v3_1":36,"cvss_v4_0":9},{"baseScore":37,"baseSeverity":9,"vectorString":38,"impactScore":39,"exploitabilityScore":40},5.5,"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",6,4.6,[42,58],{"ecosystem":43,"name":44,"vendor":45,"product":44,"cpe_part":9,"purl_type":46,"purl_namespace":45,"purl_name":44,"source":9,"versions":47},"Debian","linux","debian","deb",[48,54,57],{"version":49,"is_range":50,"range_type":51,"version_start":9,"version_start_type":9,"version_end":52,"version_end_type":53,"fixed_in":9},"lt6_1_129_1",true,"ecosystem","6.1.129-1","excluding",{"version":55,"is_range":50,"range_type":51,"version_start":9,"version_start_type":9,"version_end":56,"version_end_type":53,"fixed_in":9},"lt6_10_7_1","6.10.7-1",{"version":55,"is_range":50,"range_type":51,"version_start":9,"version_start_type":9,"version_end":56,"version_end_type":53,"fixed_in":9},{"ecosystem":43,"name":59,"vendor":45,"product":59,"cpe_part":9,"purl_type":46,"purl_namespace":45,"purl_name":59,"source":9,"versions":60},"linux-6.1",[61],{"version":62,"is_range":50,"range_type":51,"version_start":9,"version_start_type":9,"version_end":63,"version_end_type":53,"fixed_in":9},"lt6_1_129_1~deb11u1","6.1.129-1~deb11u1"]