Node down exploit?

Erwin123

Member
May 14, 2008
207
0
16
One of my nodes went just down.
I saw this message:

Jan 21 16:58:00 node4 kernel: Pid: 10648, comm: exploit Not tainted 2.6.24-7-pve #1 ovz005
Jan 21 16:58:00 node4 kernel: RIP: 0010:[<ffffffff802e06dd>] [<ffffffff802e06dd>] fasync_helper+0x4d/0x150
Jan 21 16:58:00 node4 kernel: RSP: 0000:ffff8100453fbe68 EFLAGS: 00010006
Jan 21 16:58:00 node4 kernel: RAX: 0000000000000202 RBX: ffff8101f4d6e800 RCX: 0000000000000040
Jan 21 16:58:00 node4 kernel: RDX: 0000000000000202 RSI: 0000080000000000 RDI: ffffffff805fefb8
Jan 21 16:58:00 node4 kernel: RBP: ffff8101f4d6e800 R08: 0000000000000000 R09: 00000000bfd16928
Jan 21 16:58:00 node4 kernel: R10: ffff8100453fa000 R11: 0000000000000000 R12: 0000000000000000
Jan 21 16:58:00 node4 kernel: R13: 0000000000000000 R14: 0000000000000040 R15: 00000000ffffffff
Jan 21 16:58:00 node4 kernel: FS: 0000000000000000(0000) GS:ffff81032cf1e880(0063) knlGS:00000000b7e096c0
Jan 21 16:58:00 node4 kernel: CS: 0010 DS: 002b ES: 002b CR0: 000000008005003b
Jan 21 16:58:00 node4 kernel: CR2: 0000080000000010 CR3: 000000011a7d9000 CR4: 00000000000026e0
Jan 21 16:58:00 node4 kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Jan 21 16:58:00 node4 kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Jan 21 16:58:00 node4 kernel: Process exploit (pid: 10648, veid=125, threadinfo ffff8100453fa000, task ffff8100114131c0)
Jan 21 16:58:00 node4 kernel: Stack: ffff8100453fbd38 ffff8101f4d6e800 ffff8101f4d6e800 ffff8102ec23d350
Jan 21 16:58:00 node4 kernel: 0000000000000000 0000000000000000 00000000ffffffff ffffffff802d938b
Jan 21 16:58:00 node4 kernel: ffff81031ac511e0 ffff8101f4d6e800 ffff8101f4d6e800 ffff8102ec23d290
Jan 21 16:58:00 node4 kernel: Call Trace:
Jan 21 16:58:00 node4 kernel: [<ffffffff802d938b>] pipe_rdwr_fasync+0x5b/0xc0
Jan 21 16:58:00 node4 kernel: [<ffffffff802d9a90>] pipe_rdwr_release+0x20/0x50
Jan 21 16:58:00 node4 kernel: [<ffffffff802d3845>] __fput+0xb5/0x1d0
Jan 21 16:58:00 node4 kernel: [<ffffffff802cf95b>] filp_close+0x5b/0x90
Jan 21 16:58:00 node4 kernel: [<ffffffff802cfa41>] sys_close+0xb1/0x120
Jan 21 16:58:00 node4 kernel: [<ffffffff8022aac2>] ia32_sysret+0x0/0xa
Jan 21 16:58:00 node4 kernel:
Jan 21 16:58:00 node4 kernel:
Jan 21 16:58:00 node4 kernel: Code: 48 39 5e 10 4c 89 f2 75 14 66 90 e9 83 00 00 00 0f 1f 00 48
Jan 21 16:58:00 node4 kernel: RSP <ffff8100453fbe68>
Jan 21 16:58:00 node4 kernel: ---[ end trace 81999ee5a8f12947 ]---
Jan 21 16:58:00 node4 kernel: note: exploit[10648] exited with preempt_count 1

What does this mean?
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!