System panic soon after 'Attempt to release' kernel error

Solution Verified - Updated -

Issue

  • System panics very soon after either of these messages
    IPv4: Attempt to release alive inet socket [kernel address]
    IPv4: Attempt to release TCP socket in state 1 [kernel address]
    Note: state could be random numeric value
  • System generated a vmcore soon after above messages with stack such as:
BUG: unable to handle kernel NULL pointer dereference at 0000000000000010
IP: [<ffffffffb0f0b183>] sock_has_perm+0x43/0x90
...
[<ffffffffb0f0b2b3>] selinux_socket_recvmsg+0x23/0x30
[<ffffffffb0f086bc>] security_socket_recvmsg+0x1c/0x20
[<ffffffffb123267c>] sock_aio_read.part.9+0xdc/0x170
[<ffffffffb0f0a98c>] ? avc_has_perm_flags+0xdc/0x1c0
[<ffffffffb0e6437d>] ? core_sys_select+0x26d/0x340
[<ffffffffb1232731>] sock_aio_read+0x21/0x30
[<ffffffffb0e4c5e3>] do_sync_read+0x93/0xe0
  • System generated a vmcore soon after Attempt to release error followed by warning in net/ipv4/af_inet.c:152 inet_sock_destruct+0x1a9 with stack such as:
[<ffffffff94edc2e9>] ? inet_sock_destruct+0x1a9/0x1e0
[<ffffffff9489bd3a>] __warn+0xfa/0x100
[<ffffffff9489be5d>] warn_slowpath_null+0x1d/0x20
[<ffffffff94edc2e9>] inet_sock_destruct+0x1a9/0x1e0
[<ffffffff94ecde35>] udp_destruct_sock+0x85/0xa0
[<ffffffff94e37bd9>] __sk_destruct+0x29/0x180
[<ffffffff9495ade8>] rcu_process_callbacks+0x1d8/0x570
[<ffffffff948a5695>] __do_softirq+0xf5/0x280

Environment

  • Red Hat Enterprise Linux 7 (RHEL7)
  • Red Hat Enterprise Linux 8 (RHEL8)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content