Fix for CVE-2011-4622 ??

[adoII]

Hi,

on Saturday we had a proxmox 1.9 server becoming inresponsive due to CVE-2011-4622 .

Is there a fix for proxmox 1.9 ? What would be the best way to fix it ?

Our logs shopw this:

san06:/var/log# cat /tmp/1|less
san06:/var/log# cat /tmp/1
Apr 21 11:33:33 san06 kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000128
Apr 21 11:33:33 san06 kernel: IP: [<ffffffffa03a04d4>] kvm_set_irq+0x65/0x109 [kvm]
Apr 21 11:33:33 san06 kernel: PGD 18084f5067 PUD 180872c067 PMD 0 
Apr 21 11:33:33 san06 kernel: Oops: 0000 [#1] SMP 
Apr 21 11:33:33 san06 kernel: last sysfs file: /sys/kernel/mm/ksm/run
Apr 21 11:33:33 san06 kernel: CPU 0 
Apr 21 11:33:33 san06 kernel: Modules linked in: xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack iptable_filter ip_tables x_tables vhost_net kvm_intel kvm ib_iser rdma_cm ib_cm iw_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd exportfs nfs lockd fscache nfs_acl auth_rpcgss sunrpc 8021q garp bridge stp bonding snd_pcm snd_timer snd soundcore snd_page_alloc i2c_i801 serio_raw tpm_tis tpm tpm_bios psmouse pcspkr joydev i7core_edac edac_core ioatdma igb usbhid hid megaraid_sas ixgbe dca mdio [last unloaded: scsi_wait_scan]
Apr 21 11:33:33 san06 kernel:
Apr 21 11:33:33 san06 kernel: Pid: 51, comm: events/0 Not tainted 2.6.35-2-pve #1 X8DTU-6+/X8DTU-6+
Apr 21 11:33:33 san06 kernel: RIP: 0010:[<ffffffffa03a04d4>]  [<ffffffffa03a04d4>] kvm_set_irq+0x65/0x109 [kvm]
Apr 21 11:33:33 san06 kernel: RSP: 0018:ffff880c09b29d20  EFLAGS: 00010246
Apr 21 11:33:33 san06 kernel: RAX: ffff8802f1deee40 RBX: ffff8802f1def1a0 RCX: 0000000000000001
Apr 21 11:33:33 san06 kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff8802f1deee40
Apr 21 11:33:33 san06 kernel: RBP: ffff880c09b29e00 R08: ffff880c09b28000 R09: 0000000000000000
Apr 21 11:33:33 san06 kernel: R10: ffff880001e15800 R11: ffff88180746bb50 R12: 0000000000000018
Apr 21 11:33:33 san06 kernel: R13: 0000000000000001 R14: 0000000000000000 R15: ffff880c09b20000
Apr 21 11:33:33 san06 kernel: FS:  0000000000000000(0000) GS:ffff880001e00000(0000) knlGS:0000000000000000
Apr 21 11:33:33 san06 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Apr 21 11:33:33 san06 kernel: CR2: 0000000000000128 CR3: 00000018086dc000 CR4: 00000000000026e0
Apr 21 11:33:33 san06 kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Apr 21 11:33:33 san06 kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Apr 21 11:33:33 san06 kernel: Process events/0 (pid: 51, threadinfo ffff880c09b28000, task ffff880c09b20000)
Apr 21 11:33:33 san06 kernel: Stack:
Apr 21 11:33:33 san06 kernel: ffff880001e15800 ffff880c09b20000 ffff880c09b29d70 ffff8802f1deee40
Apr 21 11:33:33 san06 kernel: <0> ffff880001e15800 ffff881809ef3800 ffff880001e15800 0000000000000000
Apr 21 11:33:33 san06 kernel: <0> ffff881809ef3800 ffff880001e15800 ffff880c09b29e20 ffffffff814b4aad
Apr 21 11:33:33 san06 kernel: Call Trace:
Apr 21 11:33:33 san06 kernel: [<ffffffff814b4aad>] ? schedule+0x58f/0x5f4
Apr 21 11:33:33 san06 kernel: [<ffffffff814b66ce>] ? common_interrupt+0xe/0x13
Apr 21 11:33:33 san06 kernel: [<ffffffffa03a10d3>] irqfd_inject+0x25/0x3a [kvm]
Apr 21 11:33:33 san06 kernel: [<ffffffff810683ab>] worker_thread+0x1a9/0x24d
Apr 21 11:33:33 san06 kernel: [<ffffffff814b4aad>] ? schedule+0x58f/0x5f4
Apr 21 11:33:33 san06 kernel: [<ffffffffa03a10ae>] ? irqfd_inject+0x0/0x3a [kvm]
Apr 21 11:33:33 san06 kernel: [<ffffffff8106c0e8>] ? autoremove_wake_function+0x0/0x3d
Apr 21 11:33:33 san06 kernel: [<ffffffff81068202>] ? worker_thread+0x0/0x24d
Apr 21 11:33:33 san06 kernel: [<ffffffff8106bc00>] kthread+0x82/0x8a
Apr 21 11:33:33 san06 kernel: [<ffffffff8100ab24>] kernel_thread_helper+0x4/0x10
Apr 21 11:33:33 san06 kernel: [<ffffffff8106bb7e>] ? kthread+0x0/0x8a
Apr 21 11:33:33 san06 kernel: [<ffffffff8100ab20>] ? kernel_thread_helper+0x0/0x10
Apr 21 11:33:33 san06 kernel: Code: 85 db 74 19 48 8b 7b 08 44 89 f1 44 89 ea 44 89 e6 ff 13 48 83 c3 10 48 83 3b 00 eb e5 48 8b 85 38 ff ff ff 48 8b 90 38 24 00 00 <44> 3b a2 28 01 00 00 72 0b 31 db 41 83 cc ff 45 31 ff eb 77 44 
Apr 21 11:33:33 san06 kernel: RIP  [<ffffffffa03a04d4>] kvm_set_irq+0x65/0x109 [kvm]
Apr 21 11:33:33 san06 kernel: RSP <ffff880c09b29d20>
Apr 21 11:33:33 san06 kernel: CR2: 0000000000000128
Apr 21 11:33:33 san06 kernel: ---[ end trace b631d22fe7dfd09e ]---

 

[tom]

as far as I see here, https://rhn.redhat.com/errata/RHSA-2012-0350.html, there is a fix in the latest kernel.

but its not available for 1.9, only for 2.0.

1.9 is obsolete anyways, so I suggest you plan your upgrade to 2.0

see http://pve.proxmox.com/wiki/Upgrade_from_1.9_to_2.0

 

[apmuthu]

https://access.redhat.com/security/cve/CVE-2011-4622

which files do we need for Proxmox v1.9 that are in v2.0 kernel that addresses this issue?