First published: Thu Dec 29 2011(Updated: )
"When parsing the FAC_NATIONAL_DIGIS facilities field, it's possible for a remote host to provide more digipeaters than expected, resulting in heap corruption. Check against ROSE_MAX_DIGIS to prevent overflows, and abort facilities parsing on failure. Additionally, when parsing the FAC_CCITT_DEST_NSAP and FAC_CCITT_SRC_NSAP facilities fields, a remote host can provide a length of less than 10, resulting in an underflow in a memcpy size, causing a kernel panic due to massive heap corruption. A length of greater than 20 results in a stack overflow of the callsign array. Abort facilities parsing on these invalid length values." These issues may both result in code execution. They may be triggered by a remote attacker if the victim has a listening ROSE socket, or by a local attacker (for privilege escalation) if a ROSE device exists (e.g. rose0). Ben Hutchings followed up with a patch [2] that resolves a number of other ROSE issues related to lack of size field validation, some of which may also result in heap corruption. [1] <a href="http://marc.info/?l=linux-netdev&m=130060344616926">http://marc.info/?l=linux-netdev&m=130060344616926</a> [2] <a href="http://marc.info/?l=linux-netdev&m=130063972406389&w=2">http://marc.info/?l=linux-netdev&m=130063972406389&w=2</a> Acknowledgements: Red Hat would like to thank Dan Rosenberg for reporting this issue.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
debian/linux-2.6 | ||
Linux kernel | =2.6.38-rc7 | |
Linux kernel | =2.6.38-rc6 | |
Linux kernel | =2.6.38-rc4 | |
Linux kernel | =2.6.38.3 | |
Linux kernel | <=2.6.38.8 | |
Linux kernel | =2.6.38-rc3 | |
Linux kernel | =2.6.38-rc5 | |
Linux kernel | =2.6.38-rc2 | |
Linux kernel | =2.6.38.6 | |
Linux kernel | =2.6.38.1 | |
Linux kernel | =2.6.38-rc1 | |
Linux kernel | =2.6.38.5 | |
Linux kernel | =2.6.38.2 | |
Linux kernel | =2.6.38 | |
Linux kernel | =2.6.38-rc8 | |
Linux kernel | =2.6.38.4 | |
Linux kernel | =2.6.38.7 | |
Linux Kernel | <=2.6.38.8 | |
Linux Kernel | =2.6.38 | |
Linux Kernel | =2.6.38-rc1 | |
Linux Kernel | =2.6.38-rc2 | |
Linux Kernel | =2.6.38-rc3 | |
Linux Kernel | =2.6.38-rc4 | |
Linux Kernel | =2.6.38-rc5 | |
Linux Kernel | =2.6.38-rc6 | |
Linux Kernel | =2.6.38-rc7 | |
Linux Kernel | =2.6.38-rc8 | |
Linux Kernel | =2.6.38.1 | |
Linux Kernel | =2.6.38.2 | |
Linux Kernel | =2.6.38.3 | |
Linux Kernel | =2.6.38.4 | |
Linux Kernel | =2.6.38.5 | |
Linux Kernel | =2.6.38.6 | |
Linux Kernel | =2.6.38.7 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2011-1493 is classified as a moderate severity vulnerability due to potential heap corruption.
To mitigate CVE-2011-1493, ensure that the software is updated to a patched version of the Linux Kernel beyond 2.6.38.7.
CVE-2011-1493 is a heap overflow vulnerability that can be triggered by an unexpected number of digipeaters.
CVE-2011-1493 affects Linux Kernel versions 2.6.38 and earlier, including various 2.6.38 release candidates.
Yes, CVE-2011-1493 can be exploited remotely by delivering crafted packets to the vulnerable system.