[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKHoSAuo37CMpkkij7SzPgra4VqJKUMWVV7rd=Mq6r5hXLmhvw@mail.gmail.com>
Date: Mon, 2 Dec 2024 10:29:29 +0800
From: cheung wall <zzqq0103.hey@...il.com>
To: linux-kernel@...r.kernel.org
Subject: kernel panic: Failed to create the TCP control socket
Hello,
I am writing to report a potential vulnerability identified in the
Linux Kernel version 2.6.32, specifically on the PowerPC architecture.
This issue was discovered using our custom vulnerability discovery
tool.
Detailed report:
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver hub
Freescale Elo / Elo Plus DMA driver
NET: Registered protocol family 2
Kernel panic - not syncing: Failed to create the TCP control socket.
VM DIAGNOSIS:
15:22:24 Registers:
Failed readin g regs: dial tcp 127.0.0.1:4441: connect: connection refused
Root Cause:
The root cause of this kernel panic is the failure to create a TCP
control socket during early network initialization, which prevents the
system from proceeding with networking operations. This could be due
to insufficient system resources (e.g., memory or file descriptors),
improper initialization of the networking subsystem, or misconfigured
kernel options that prevent the correct setup of the network stack or
drivers. The absence of the critical TCP socket halts the networking
stack, resulting in the kernel panic.
We would appreciate it if the kernel maintainers could investigate
this issue further. Please let us know if additional details or steps
to reproduce are needed. We are happy to assist in any way we can.
Thank you for your time and attention.
Best regards
Wall
Powered by blists - more mailing lists