CVE-2011-1593: Integer Overflow

Published Apr 19, 2011
·
Updated

A signedness issue has been found in nextpidmap() function when the "last" parameter is negative as nextpidmap() just quietly accepted whatever "last" pid that was passed in, which is not all that safe when one of the users is /proc.

Setting fpos to negative value when accessing /proc via readdir()/getdents() resulted in sign extension of this value when map pointer was being constructed.

This later lead to #GP becasue the final pointer was not cannonical (x8664).

map = &pidns->pidmap[(last + 1)/BITSPERPAGE]; ffffffff810ac3b4: 48 63 f6 movslq %esi,%rsi <- sign extension (fpos+-) ffffffff810ac3b7: 81 e2 ff 7f 00 00 and $0x7fff,%edx ffffffff810ac3bd: 48 c1 ee 0f shr $0xf,%rsi ffffffff810ac3c1: 48 c1 e6 04 shl $0x4,%rsi ffffffff810ac3c5: 48 8d 5c 37 08 lea 0x8(%rdi,%rsi,1),%rbx ... if (unlikely(!map->page)) ffffffff810ac3cc: 48 8b 7b 08 mov 0x8(%rbx),%rdi <- #GP

Only x8664 architecture seems to be vulnerable to this particular issue (tested ppc64, s390x, ia64).

Reference: http://groups.google.com/group/fa.linux.kernel/browsethread/thread/93c1088451fd3522/4a28ecb7f755a88d?#4a28ecb7f755a88d

Upstream commit: http://git.kernel.org/linus/c78193e9 http://git.kernel.org/linus/d8bdc59f

Acknowledgements:

Red Hat would like to thank Robert Swiecki for reporting this issue.

Other sources

Multiple integer overflows in the nextpidmap function in kernel/pid.c in the Linux kernel before 2.6.38.4 allow local users to cause a denial of service (system crash) via a crafted (1) getdents or (2) readdir system call.

Launchpad

Affected Software

9 affected components
debian/linux-2.6
Linux Linux kernel<2.6.38.4
redhat Enterprise Linux Server=5.0
redhat Enterprise Linux Workstation=5.0
redhat Enterprise Linux=5.0
redhat Enterprise Linux Desktop=5.0
redhat Enterprise Linux Eus=5.6
redhat Enterprise Linux Aus=5.6
Canonical Ubuntu Linux=8.04

Event History

Apr 19, 2011
Data Sourced
via Red Hat·11:42 AM
DescriptionSeverityAffected Software
May 3, 2011
CVE Published
via MITRE·08:00 PM
Data Sourced
via MITRE·08:00 PM
Description
Jan 11, 2024
Data Sourced
via Launchpad·09:56 PM
Description
Sep 19, 2024
Data Sourced
via Ubuntu·10:44 PM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2011-1593?

CVE-2011-1593 is classified as a medium severity vulnerability due to its potential impact on system security.

2

How do I fix CVE-2011-1593?

To mitigate CVE-2011-1593, users should upgrade to a version of the Linux kernel that is beyond 2.6.38.4.

3

Who is affected by CVE-2011-1593?

CVE-2011-1593 affects users of Linux kernel versions prior to 2.6.38.4, particularly those running older distributions of Red Hat Enterprise Linux and Ubuntu.

4

What type of vulnerability is CVE-2011-1593?

CVE-2011-1593 is a signedness issue found in the next_pidmap() function of the Linux kernel.

5

Can CVE-2011-1593 be exploited remotely?

CVE-2011-1593 can be exploited if an attacker has local access to the vulnerable system, increasing the risk of privilege escalation.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203