CVE-2024-26614

Description

In the Linux kernel, the following vulnerability has been resolved: tcp: make sure init the accept_queue's spinlocks once When I run syz's reproduction C program locally, it causes the following issue: pvqspinlock: lock 0xffff9d181cd5c660 has corrupted value 0x0! WARNING: CPU: 19 PID: 21160 at __pv_queued_spin_unlock_slowpath (kernel/locking/qspinlock_paravirt.h:508) Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2011 RIP: 0010:__pv_queued_spin_unlock_slowpath (kernel/locking/qspinlock_paravirt.h:508) Code: 73 56 3a ff 90 c3 cc cc cc cc 8b 05 bb 1f 48 01 85 c0 74 05 c3 cc cc cc cc 8b 17 48 89 fe 48 c7 c7 30 20 ce 8f e8 ad 56 42 ff <0f> 0b c3 cc cc cc cc 0f 0b 0f 1f 40 00 90 90 90 90 90 90 90 90 90 RSP: 0018:ffffa8d200604cb8 EFLAGS: 00010282 RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffff9d1ef60e0908 RDX: 00000000ffffffd8 RSI: 0000000000000027 RDI: ffff9d1ef60e0900 RBP: ffff9d181cd5c280 R08: 0000000000000000 R09: 00000000ffff7fff R10: ffffa8d200604b68 R11: ffffffff907dcdc8 R12: 0000000000000000 R13: ffff9d181cd5c660 R14: ffff9d1813a3f330 R15: 0000000000001000 FS: 00007fa110184640(0000) GS:ffff9d1ef60c0000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020000000 CR3: 000000011f65e000 CR4: 00000000000006f0 Call Trace: <IRQ> _raw_spin_unlock (kernel/locking/spinlock.c:186) inet_csk_reqsk_queue_add (net/ipv4/inet_connection_sock.c:1321) inet_csk_complete_hashdance (net/ipv4/inet_connection_sock.c:1358) tcp_check_req (net/ipv4/tcp_minisocks.c:868) tcp_v4_rcv (net/ipv4/tcp_ipv4.c:2260) ip_protocol_deliver_rcu (net/ipv4/ip_input.c:205) ip_local_deliver_finish (net/ipv4/ip_input.c:234) __netif_receive_skb_one_core (net/core/dev.c:5529) process_backlog (./include/linux/rcupdate.h:779) __napi_poll (net/core/dev.c:6533) net_rx_action (net/core/dev.c:6604) __do_softirq (./arch/x86/include/asm/jump_label.h:27) do_softirq (kernel/softirq.c:454 kernel/softirq.c:441) </IRQ> <TASK> __local_bh_enable_ip (kernel/softirq.c:381) __dev_queue_xmit (net/core/dev.c:4374) ip_finish_output2 (./include/net/neighbour.h:540 net/ipv4/ip_output.c:235) __ip_queue_xmit (net/ipv4/ip_output.c:535) __tcp_transmit_skb (net/ipv4/tcp_output.c:1462) tcp_rcv_synsent_state_process (net/ipv4/tcp_input.c:6469) tcp_rcv_state_process (net/ipv4/tcp_input.c:6657) tcp_v4_do_rcv (net/ipv4/tcp_ipv4.c:1929) __release_sock (./include/net/sock.h:1121 net/core/sock.c:2968) release_sock (net/core/sock.c:3536) inet_wait_for_connect (net/ipv4/af_inet.c:609) __inet_stream_connect (net/ipv4/af_inet.c:702) inet_stream_connect (net/ipv4/af_inet.c:748) __sys_connect (./include/linux/file.h:45 net/socket.c:2064) __x64_sys_connect (net/socket.c:2073 net/socket.c:2070 net/socket.c:2070) do_syscall_64 (arch/x86/entry/common.c:51 arch/x86/entry/common.c:82) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:129) RIP: 0033:0x7fa10ff05a3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d ab a3 0e 00 f7 d8 64 89 01 48 RSP: 002b:00007fa110183de8 EFLAGS: 00000202 ORIG_RAX: 000000000000002a RAX: ffffffffffffffda RBX: 0000000020000054 RCX: 00007fa10ff05a3d RDX: 000000000000001c RSI: 0000000020000040 RDI: 0000000000000003 RBP: 00007fa110183e20 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000202 R12: 00007fa110184640 R13: 0000000000000000 R14: 00007fa10fe8b060 R15: 00007fff73e23b20 </TASK> The issue triggering process is analyzed as follows: Thread A Thread B tcp_v4_rcv //receive ack TCP packet inet_shutdown tcp_check_req tcp_disconnect //disconnect sock ... tcp_set_state(sk, TCP_CLOSE) inet_csk_complete_hashdance ... inet_csk_reqsk_queue_add ---truncated---

CVSS Metrics

• v3.1•HIGH•Score: 7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS Trends

Current EPSS score: 0.18%• Percentile: 8%

Techniques & Countermeasures

• CWE-667•Improper Locking

  The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

Affected Systems

• debian•linux

  < 5.10.216-1 | < 6.1.76-1 | < 6.6.15-1 | < 6.6.15-1

• ubuntu•linux

  all | < 4.4.0-254.288 | < 4.15.0-225.237 | < 5.4.0-182.202 | < 5.15.0-106.116

• ubuntu•linux-allwinner-5.19

  all

• ubuntu•linux-aws

  < 4.4.0-1131.137 | < 4.4.0-1169.184 | < 4.15.0-1168.181 | < 5.4.0-1125.135 | < 5.15.0-1061.67

• ubuntu•linux-aws-5.0

  all

• ubuntu•linux-aws-5.11

  all

• ubuntu•linux-aws-5.13

  all

• ubuntu•linux-aws-5.15

  < 5.15.0-1061.67~20.04.1

• ubuntu•linux-aws-5.19

  all

• ubuntu•linux-aws-5.3

  all

• ubuntu•linux-aws-5.4

  < 5.4.0-1125.135~18.04.1

• ubuntu•linux-aws-5.8

  all

• ubuntu•linux-aws-6.2

  all

• ubuntu•linux-aws-6.5

  < 6.5.0-1020.20~22.04.1

• ubuntu•linux-aws-fips

  < 4.15.0-2107.113 | all | < 5.4.0-1125.135+fips1 | < 5.15.0-1061.67+fips1

• ubuntu•linux-aws-hwe

  < 4.15.0-1168.181~16.04.1

• ubuntu•linux-azure

  < 4.15.0-1177.192~14.04.1 | < 4.15.0-1177.192~16.04.1 | all | < 5.4.0-1130.137 | < 5.15.0-1063.72

• ubuntu•linux-azure-4.15

  < 4.15.0-1177.192

• ubuntu•linux-azure-5.11

  all

• ubuntu•linux-azure-5.13

  all

• ubuntu•linux-azure-5.15

  < 5.15.0-1063.72~20.04.1

• ubuntu•linux-azure-5.19

  all

• ubuntu•linux-azure-5.3

  all

• ubuntu•linux-azure-5.4

  < 5.4.0-1130.137~18.04.1

• ubuntu•linux-azure-5.8

  all

• ubuntu•linux-azure-6.2

  all

• ubuntu•linux-azure-6.5

  < 6.5.0-1021.22~22.04.1

• ubuntu•linux-azure-edge

  all

• ubuntu•linux-azure-fde

  all | < 5.15.0-1063.72.1 | all

• ubuntu•linux-azure-fde-5.19

  all

• ubuntu•linux-azure-fde-6.2

  all

• ubuntu•linux-azure-fde-6.8

  all

• ubuntu•linux-azure-fips

  < 4.15.0-2086.92 | all | < 5.4.0-1130.137+fips1 | < 5.15.0-1063.72+fips1

• ubuntu•linux-bluefield

  all | < 5.4.0-1085.92 | < 5.15.0-1043.45

• ubuntu•linux-fips

  < 4.4.0-1101.108 | all | < 4.15.0-1123.134 | < 5.4.0-1099.109 | < 5.15.0-106.116+fips1

• ubuntu•linux-gcp

  < 4.15.0-1162.179~16.04.1 | all | < 5.4.0-1129.138 | < 5.15.0-1059.67

• ubuntu•linux-gcp-4.15

  < 4.15.0-1162.179

• ubuntu•linux-gcp-5.11

  all

• ubuntu•linux-gcp-5.13

  all

• ubuntu•linux-gcp-5.15

  < 5.15.0-1059.67~20.04.1

• ubuntu•linux-gcp-5.19

  all

• ubuntu•linux-gcp-5.3

  all

• ubuntu•linux-gcp-5.4

  < 5.4.0-1129.138~18.04.1

• ubuntu•linux-gcp-5.8

  all

• ubuntu•linux-gcp-6.2

  all

• ubuntu•linux-gcp-6.5

  < 6.5.0-1020.20~22.04.1

• ubuntu•linux-gcp-fips

  < 4.15.0-2070.75 | all | < 5.4.0-1129.138+fips1 | < 5.15.0-1059.67+fips1

• ubuntu•linux-gke

  all | < 5.15.0-1058.63

• ubuntu•linux-gke-4.15

  all

• ubuntu•linux-gke-5.15

  all

Showing first 50 affected entries in server-rendered view.

References (23)

• https://git.kernel.org/stable/c/bc99dcedd2f422d602516762b96c8ef1ae6b2882
• https://git.kernel.org/stable/c/d86cc6ab33b085eaef27ea88b78fc8e2375c0ef3
• https://git.kernel.org/stable/c/b1e0a68a0cd2a83259c444f638b417a8fffc6855
• https://git.kernel.org/stable/c/168e7e599860654876c2a1102a82610285c02f02
• https://git.kernel.org/stable/c/3982fe726a63fb3de6005e534e2ac8ca7e0aca2a
• https://git.kernel.org/stable/c/198bc90e0e734e5f98c3d2833e8390cac3df61b2
• https://lists.debian.org/debian-lts-announce/2024/06/msg00017.html
• https://ubuntu.com/security/CVE-2024-26614
• https://git.kernel.org/linus/198bc90e0e734e5f98c3d2833e8390cac3df61b2
• https://www.cve.org/CVERecord?id=CVE-2024-26614
• https://ubuntu.com/security/notices/USN-6766-1
• https://ubuntu.com/security/notices/USN-6766-2
• https://ubuntu.com/security/notices/USN-6774-1
• https://ubuntu.com/security/notices/USN-6776-1
• https://ubuntu.com/security/notices/USN-6777-1
• https://ubuntu.com/security/notices/USN-6778-1
• https://ubuntu.com/security/notices/USN-6766-3
• https://ubuntu.com/security/notices/USN-6777-2
• https://ubuntu.com/security/notices/USN-6777-3
• https://ubuntu.com/security/notices/USN-6777-4
• https://ubuntu.com/security/notices/USN-6795-1
• https://ubuntu.com/security/notices/USN-6828-1
• https://security-tracker.debian.org/tracker/CVE-2024-26614