Skip to content
Fencer Intel
low 2.1

CVE-2011-1044 json

The ib_uverbs_poll_cq function in drivers/infiniband/core/uverbs_cmd.c in the Linux kernel before 2.6.37 does not initialize a certain resp…

published 2011-02-18 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-1060

cvss
2.1
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 32%
public exploits
0
none known

Summary

The ib_uverbs_poll_cq function in drivers/infiniband/core/uverbs_cmd.c in the Linux kernel before 2.6.37 does not initialize a certain response buffer, which allows local users to obtain potentially sensitive information from kernel memory via vectors that cause this buffer to be only partially filled, a different vulnerability than CVE-2010-4649.

Patch / fix

  • linux linux_kernel 2.6.37
  • kernel RHEL 5 2.6.18-238.19.1.el5
  • kernel-PAE RHEL 5 2.6.18-238.19.1.el5
  • kernel-xen RHEL 5 2.6.18-238.19.1.el5
  • kernel-kdump RHEL 5 2.6.18-238.19.1.el5
  • kernel-debuginfo-common RHEL 5 2.6.18-238.19.1.el5
  • kernel RHEL 6 2.6.32-71.29.1.el6
  • perf RHEL 6 2.6.32-71.29.1.el6
  • kernel-kdump RHEL 6 2.6.32-71.29.1.el6

red hat advisories RHSA-2011:0927RHSA-2011:0498RHSA-2011:0330

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2011-1044 updated cvss 6.9

kernel: IB/uverbs: Handle large number of entries in poll CQ

  • Red Hat Enterprise Linux 4 kernel
    affected: no fix available
  • Red Hat MRG Realtime for RHEL 5 Server perf 2.6.33.7-rt29.55.el5rt, kernel-rt 2.6.33.7-rt29.55.el5rt, kernel-rt-trace 2.6.33.7-rt29.55.el5rt, kernel-rt-vanilla 2.6.33.7-rt29.55.el5rt, kernel-rt-debuginfo-common 2.6.33.7-rt29.55.el5rt
    fixed: vendor fix RHSA-2011:0330
  • Red Hat Enterprise Linux (v. 5.6.z server) kernel 2.6.18-238.19.1.el5, kernel-PAE 2.6.18-238.19.1.el5, kernel-xen 2.6.18-238.19.1.el5, kernel-kdump 2.6.18-238.19.1.el5, kernel-debuginfo-common 2.6.18-238.19.1.el5
    fixed: vendor fix RHSA-2011:0927
  • Red Hat Enterprise Linux Desktop (v. 6) perf 2.6.32-71.29.1.el6, kernel 2.6.32-71.29.1.el6, kernel-firmware 2.6.32-71.29.1.el6, kernel-debuginfo-common-i686 2.6.32-71.29.1.el6, kernel-debuginfo-common-x86_64 2.6.32-71.29.1.el6 Red Hat Enterprise Linux HPC Node (v. 6) perf 2.6.32-71.29.1.el6, kernel 2.6.32-71.29.1.el6, kernel-firmware 2.6.32-71.29.1.el6, kernel-debuginfo-common-x86_64 2.6.32-71.29.1.el6 Red Hat Enterprise Linux Server (v. 6) perf 2.6.32-71.29.1.el6, kernel 2.6.32-71.29.1.el6, kernel-kdump 2.6.32-71.29.1.el6, kernel-firmware 2.6.32-71.29.1.el6, kernel-bootwrapper 2.6.32-71.29.1.el6, kernel-debuginfo-common-i686 2.6.32-71.29.1.el6, +3 more Red Hat Enterprise Linux Workstation (v. 6) perf 2.6.32-71.29.1.el6, kernel 2.6.32-71.29.1.el6, kernel-firmware 2.6.32-71.29.1.el6, kernel-debuginfo-common-i686 2.6.32-71.29.1.el6, kernel-debuginfo-common-x86_64 2.6.32-71.29.1.el6
    fixed: vendor fix RHSA-2011:0498
  • Red Hat Enterprise Linux (v. 5.6.z server) kernel-headers 2.6.18-238.19.1.el5 Red Hat Enterprise Linux Desktop (v. 6) kernel-headers 2.6.32-71.29.1.el6 Red Hat Enterprise Linux HPC Node (v. 6) kernel-headers 2.6.32-71.29.1.el6 Red Hat Enterprise Linux Server (v. 6) kernel-headers 2.6.32-71.29.1.el6 Red Hat Enterprise Linux Workstation (v. 6) kernel-headers 2.6.32-71.29.1.el6
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.39% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:P/I:N/A:N

Classification

Weakness
  • CWE-909 Missing Initialization of Resource
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.