0b
90 eb b2 e8 10 6d c6 f7 4c 89 e7 be 04 00 00 00 e8 63 e7 d2 RSP:
0018:ffffc900032d7848 EFLAGS: 00010246 RAX: ffffffff89cd0035 RBX:
0000000000000001 RCX: 0000000000040000 RDX: ffffc90004de1000 RSI:
000000000003ffff RDI: 0000000000040000 RBP: 1ffff1100439ac26 R08:
ffffffff89ccffe3 R09: 1ffff1100439ac28 R10: dffffc0000000000 R11:
ffffed100439ac29 R12: ffff888021cd6140 R13: dffffc0000000000 R14:
ffff88802a9bf5c0 R15: ffff888021cd6130 FS: 00007f3b823f16c0(0000)
GS:ffff8880b9400000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES:
0000 CR0: 0000000080050033 CR2: 00007f3b823f0ff8 CR3: 000000004674a000
CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2:
0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7:
0000000000000400 Call Trace:
![]() |
Home ▼ Bookkeeping
Online ▼ Security
Audits ▼
Managed
DNS ▼
About
Order
FAQ
Acceptable Use Policy
Dynamic DNS Clients
Configure Domains Dyanmic DNS Update Password Network
Monitor ▼
Enterprise Package
Advanced Package
Standard Package
Free Trial
FAQ
Price/Feature Summary
Order/Renew
Examples
Configure/Status Alert Profiles | ||
CVE ID: | CVE-2024-26864 |
Description: | In the Linux kernel, the following vulnerability has been resolved:
tcp: Fix refcnt handling in __inet_hash_connect(). syzbot reported a
warning in sk_nulls_del_node_init_rcu(). The commit 66b60b0c8c4a
("dccp/tcp: Unhash sk from ehash for tb2 alloc failure after
check_estalblished().") tried to fix an issue that an unconnected
socket occupies an ehash entry when bhash2 allocation fails. In such a
case, we need to revert changes done by check_established(), which
does not hold refcnt when inserting socket into ehash. So, to revert
the change, we need to __sk_nulls_add_node_rcu() instead of
sk_nulls_add_node_rcu(). Otherwise, sock_put() will cause refcnt
underflow and leak the socket. [0]: WARNING: CPU: 0 PID: 23948 at
include/net/sock.h:799 sk_nulls_del_node_init_rcu+0x166/0x1a0
include/net/sock.h:799 Modules linked in: CPU: 0 PID: 23948 Comm: syz-
executor.2 Not tainted 6.8.0-rc6-syzkaller-00159-gc055fc00c07b #0
Hardware name: Google Google Compute Engine/Google Compute Engine,
BIOS Google 01/25/2024 RIP:
0010:sk_nulls_del_node_init_rcu+0x166/0x1a0 include/net/sock.h:799
Code: e8 7f 71 c6 f7 83 fb 02 7c 25 e8 35 6d c6 f7 4d 85 f6 0f 95 c0
5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc e8 1b 6d c6 f7 90 <0f> 0b
90 eb b2 e8 10 6d c6 f7 4c 89 e7 be 04 00 00 00 e8 63 e7 d2 RSP:
0018:ffffc900032d7848 EFLAGS: 00010246 RAX: ffffffff89cd0035 RBX:
0000000000000001 RCX: 0000000000040000 RDX: ffffc90004de1000 RSI:
000000000003ffff RDI: 0000000000040000 RBP: 1ffff1100439ac26 R08:
ffffffff89ccffe3 R09: 1ffff1100439ac28 R10: dffffc0000000000 R11:
ffffed100439ac29 R12: ffff888021cd6140 R13: dffffc0000000000 R14:
ffff88802a9bf5c0 R15: ffff888021cd6130 FS: 00007f3b823f16c0(0000)
GS:ffff8880b9400000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES:
0000 CR0: 0000000080050033 CR2: 00007f3b823f0ff8 CR3: 000000004674a000
CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2:
0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7:
0000000000000400 Call Trace: |
Test IDs: | None available |
Cross References: |
Common Vulnerability Exposure (CVE) ID: CVE-2024-26864 https://git.kernel.org/stable/c/04d9d1fc428ac9f581d55118d67e0cb546701feb https://git.kernel.org/stable/c/04d9d1fc428ac9f581d55118d67e0cb546701feb https://git.kernel.org/stable/c/1b20e61d36f490319d3fbdedd410155232ab5190 https://git.kernel.org/stable/c/1b20e61d36f490319d3fbdedd410155232ab5190 https://git.kernel.org/stable/c/856baaa100cd288d3685eedae9a129c996e7e755 https://git.kernel.org/stable/c/856baaa100cd288d3685eedae9a129c996e7e755 https://git.kernel.org/stable/c/86d9b040421bbd26425f5a3edc226f57ecdecbfe https://git.kernel.org/stable/c/86d9b040421bbd26425f5a3edc226f57ecdecbfe https://git.kernel.org/stable/c/ad105cde6b261b8b05ec872fe7d1987417d7fe5a https://git.kernel.org/stable/c/ad105cde6b261b8b05ec872fe7d1987417d7fe5a |