[LU-4628] Kernel update [RHEL6.5 2.6.32-431.5.1.el6] Created: 13/Feb/14  Updated: 13/Feb/14  Resolved: 13/Feb/14

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Yang Sheng Assignee: Yang Sheng
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Related
is related to LU-4620 Kernel update [RHEL6.5 2.6.32-431.5.1... Resolved
Severity: 3
Rank (Obsolete): 12658

 Description   
  • A buffer overflow flaw was found in the way the qeth_snmp_command()
    function in the Linux kernel's QETH network device driver implementation
    handled SNMP IOCTL requests with an out-of-bounds length. A local,
    unprivileged user could use this flaw to crash the system or, potentially,
    escalate their privileges on the system. (CVE-2013-6381, Important)
  • A flaw was found in the way the get_dumpable() function return value was
    interpreted in the ptrace subsystem of the Linux kernel. When
    'fs.suid_dumpable' was set to 2, a local, unprivileged local user could
    use this flaw to bypass intended ptrace restrictions and obtain
    potentially sensitive information. (CVE-2013-2929, Low)
  • It was found that certain protocol handlers in the Linux kernel's
    networking implementation could set the addr_len value without initializing
    the associated data structure. A local, unprivileged user could use this
    flaw to leak kernel stack memory to user space using the recvmsg, recvfrom,
    and recvmmsg system calls (CVE-2013-7263, CVE-2013-7265, Low).

This update also fixes several bugs.

Bugs fixed (https://bugzilla.redhat.com/):

1028148 - CVE-2013-2929 kernel: exec/ptrace: get_dumpable() incorrect tests
1033600 - CVE-2013-6381 Kernel: qeth: buffer overflow in snmp ioctl
1035875 - CVE-2013-7263 CVE-2013-7265 Kernel: net: leakage of uninitialized memory to user-space via recv syscalls



 Comments   
Comment by Peter Jones [ 13/Feb/14 ]

I think that this is already being tracked under lu-4620

Comment by Dmitry Eremin (Inactive) [ 13/Feb/14 ]

It looks the same.

Generated at Sat Feb 10 01:44:27 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.