CVE-2014-3122

Bug Description

The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings.

Break-Fix: b291f000393f5a0b679012b39d79fbc85c018233 57e68e9cd65b4b8eb4045a1e0d0746458502554c

CVE-2014-3122

This bug was fixed in the package linux - 2.6.32-61.124

---------------
linux (2.6.32-61.124) lucid; urgency=low

[ Luis Henriques ]

* Revert "sysctl net: Keep tcp_syn_retries inside the boundary"
- LP: #1326473
* Revert "net: check net.core.somaxconn sysctl values"
- LP: #1326473

[ Upstream Kernel Changes ]

* futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr ==
uaddr2 in futex_requeue(..., requeue_pi=1)
- LP: #1326367
- CVE-2014-3153
* futex: Validate atomic acquisition in futex_lock_pi_atomic()
- LP: #1326367
- CVE-2014-3153
* futex: Always cleanup owner tid in unlock_pi
- LP: #1326367
- CVE-2014-3153
* futex: Make lookup_pi_state more robust
- LP: #1326367
- CVE-2014-3153
-- Brad Figg <email address hidden> 2014年6月04日 07:21:55 -0700

This bug was fixed in the package linux-ec2 - 2.6.32-365.79

---------------
linux-ec2 (2.6.32-365.79) lucid; urgency=low

[ Brad Figg ]

* Rebased to Ubuntu-2.6.32-61.124
-- Brad Figg <email address hidden> 2014年6月04日 15:25:02 -0700

This bug was fixed in the package linux - 3.2.0-64.97

---------------
linux (3.2.0-64.97) precise; urgency=low

[ Upstream Kernel Changes ]

* futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr ==
uaddr2 in futex_requeue(..., requeue_pi=1)
- LP: #1326367
- CVE-2014-3153
* futex: Validate atomic acquisition in futex_lock_pi_atomic()
- LP: #1326367
- CVE-2014-3153
* futex: Always cleanup owner tid in unlock_pi
- LP: #1326367
- CVE-2014-3153
* futex: Make lookup_pi_state more robust
- LP: #1326367
- CVE-2014-3153
-- Brad Figg <email address hidden> 2014年6月04日 10:48:57 -0700

This bug was fixed in the package linux-armadaxp - 3.2.0-1634.49

---------------
linux-armadaxp (3.2.0-1634.49) precise-proposed; urgency=low

[ Ike Panhc ]

* Release Tracking Bug
- LP: #1326748
* Rebase to Ubuntu-3.2.0-64.97

[ Ubuntu: 3.2.0-64.97 ]

* futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr ==
uaddr2 in futex_requeue(..., requeue_pi=1)
- LP: #1326367
- CVE-2014-3153
* futex: Validate atomic acquisition in futex_lock_pi_atomic()
- LP: #1326367
- CVE-2014-3153
* futex: Always cleanup owner tid in unlock_pi
- LP: #1326367
- CVE-2014-3153
* futex: Make lookup_pi_state more robust
- LP: #1326367
- CVE-2014-3153
-- Ike Panhc <email address hidden> 2014年6月05日 19:41:05 +0800

This bug was fixed in the package linux-ti-omap4 - 3.2.0-1449.68

---------------
linux-ti-omap4 (3.2.0-1449.68) precise; urgency=low

* Release Tracking Bug
- LP: #1326747

[ Paolo Pisati ]

* rebased on Ubuntu-3.2.0-64.97

[ Ubuntu: 3.2.0-64.97 ]

* futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr ==
uaddr2 in futex_requeue(..., requeue_pi=1)
- LP: #1326367
- CVE-2014-3153
* futex: Validate atomic acquisition in futex_lock_pi_atomic()
- LP: #1326367
- CVE-2014-3153
* futex: Always cleanup owner tid in unlock_pi
- LP: #1326367
- CVE-2014-3153
* futex: Make lookup_pi_state more robust
- LP: #1326367
- CVE-2014-3153

linux-ti-omap4 (3.2.0-1448.67) precise; urgency=low

* Release Tracking Bug
- LP: #1322135

[ Paolo Pisati ]

* rebased on Ubuntu-3.2.0-64.96
* [Config] BLK_DEV_DM_BUILTIN=y

[ Ubuntu: 3.2.0-64.96 ]

* Release Tracking Bug
- LP: #1321792
* [Config] updateconfigs after Linux v3.2.58 and v3.2.59 updates
* Revert "sparc64: Fix __copy_{to,from}_user_inatomic defines."
- LP: #1319885
* Revert "alpha: fix broken network checksum"
- LP: #1319885
* Revert "isci: fix reset timeout handling"
- LP: #1319885
* Revert "USB: serial: add usbid for dell wwan card to sierra.c"
- LP: #1319885
* mm: try_to_unmap_cluster() should lock_page() before mlocking
- LP: #1316268
- CVE-2014-3122
* net: sctp: fix skb leakage in COOKIE ECHO path of chunk->auth_chunk
- LP: #1319885
* bridge: multicast: add sanity check for query source addresses
- LP: #1319885
* net: unix: non blocking recvmsg() should not return -EINTR
- LP: #1319885
* vlan: Set correct source MAC address with TX VLAN offload enabled
- LP: #1319885
* net: socket: error on a negative msg_namelen
- LP: #1319885
* ipv6: Avoid unnecessary temporary addresses being generated
- LP: #1319885
* ipv6: ip6_append_data_mtu do not handle the mtu of the second fragment
properly
- LP: #1319885
* vhost: validate vhost_get_vq_desc return value
- LP: #1319885
- CVE-2014-0055
* xen-netback: remove pointless clause from if statement
- LP: #1319885
* ipv6: some ipv6 statistic counters failed to disable bh
- LP: #1319885
* netlink: don't compare the nul-termination in nla_strcmp
- LP: #1319885
* isdnloop: Validate NUL-terminated strings from user.
- LP: #1319885
* isdnloop: several buffer overflows
- LP: #1319885
* sparc: PCI: Fix incorrect address calculation of PCI Bridge windows on
Simba-bridges
- LP: #1319885
* sparc32: fix build failure for arch_jump_label_transform
- LP: #1319885
* sparc64: don't treat 64-bit syscall return codes as 32-bit
- LP: #1319885
* drm/i915: inverted brightness quirk for Acer Aspire 4736Z
- LP: #1319885
* drm/i915: quirk invert brightness for Acer Aspire 5336
- LP: #1319885
* w1: fix w1_send_slave dropping a slave id
- LP: #1319885
* ARM: mm: introduce present, faulting entries for PAGE_NONE
- LP: #1319885
* ARM: 7954/1: mm: remove remaining domain support from ARMv6
- LP: #1319885
* matroxfb: restore the registers M_ACC...

This bug was nominated against a series that is no longer supported, ie vivid. The bug task representing the vivid nomination is being closed as Won't Fix.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

The task "linux-flo (Ubuntu)" has expired because it has had no new comments or updates for more than three years.

If this issue is still present in an Ubuntu LTS kernel still under active support, please reopen the bug and provide updated details. If this issue was reported against an Ubuntu kernel no longer under active support but the issue still exists in a currently supported Ubuntu kernel, please open a new bug against that kernel version and provide the updated details, with a reference link to the original bug.

This action was performed by an automated process maintained by the Ubuntu Kernel Team.

The task "linux-goldfish (Ubuntu)" has expired because it has had no new comments or updates for more than three years.

If this issue is still present in an Ubuntu LTS kernel still under active support, please reopen the bug and provide updated details. If this issue was reported against an Ubuntu kernel no longer under active support but the issue still exists in a currently supported Ubuntu kernel, please open a new bug against that kernel version and provide the updated details, with a reference link to the original bug.

This action was performed by an automated process maintained by the Ubuntu Kernel Team.

The task "linux-mako (Ubuntu)" has expired because it has had no new comments or updates for more than three years.

If this issue is still present in an Ubuntu LTS kernel still under active support, please reopen the bug and provide updated details. If this issue was reported against an Ubuntu kernel no longer under active support but the issue still exists in a currently supported Ubuntu kernel, please open a new bug against that kernel version and provide the updated details, with a reference link to the original bug.

This action was performed by an automated process maintained by the Ubuntu Kernel Team.

The task "linux-lts-xenial (Ubuntu Vivid)" has been closed automatically because it was filed against an Ubuntu release that is now end-of-life.

If this issue is still present in a supported Ubuntu kernel, please open a new bug and provide updated details.

This action was performed by an automated process maintained by the Ubuntu Kernel Team.

The task "linux-mako (Ubuntu Vivid)" has been closed automatically because it was filed against an Ubuntu release that is now end-of-life.

If this issue is still present in a supported Ubuntu kernel, please open a new bug and provide updated details.

This action was performed by an automated process maintained by the Ubuntu Kernel Team.

The task "linux-snapdragon (Ubuntu Vivid)" has been closed automatically because it was filed against an Ubuntu release that is now end-of-life.

If this issue is still present in a supported Ubuntu kernel, please open a new bug and provide updated details.

This action was performed by an automated process maintained by the Ubuntu Kernel Team.

The task "linux-flo (Ubuntu Wily)" has been closed automatically because it was filed against an Ubuntu release that is now end-of-life.

If this issue is still present in a supported Ubuntu kernel, please open a new bug and provide updated details.

This action was performed by an automated process maintained by the Ubuntu Kernel Team.

The task "linux-goldfish (Ubuntu Wily)" has been closed automatically because it was filed against an Ubuntu release that is now end-of-life.

If this issue is still present in a supported Ubuntu kernel, please open a new bug and provide updated details.

This action was performed by an automated process maintained by the Ubuntu Kernel Team.

The task "linux-mako (Ubuntu Wily)" has been closed automatically because it was filed against an Ubuntu release that is now end-of-life.

If this issue is still present in a supported Ubuntu kernel, please open a new bug and provide updated details.

This action was performed by an automated process maintained by the Ubuntu Kernel Team.

The task "linux-manta (Ubuntu Wily)" has been closed automatically because it was filed against an Ubuntu release that is now end-of-life.

If this issue is still present in a supported Ubuntu kernel, please open a new bug and provide updated details.

This action was performed by an automated process maintained by the Ubuntu Kernel Team.

The task "linux-flo (Ubuntu Xenial)" has expired because it has had no new comments or updates for more than three years.

If this issue is still present in an Ubuntu LTS kernel still under active support, please reopen the bug and provide updated details. If this issue was reported against an Ubuntu kernel no longer under active support but the issue still exists in a currently supported Ubuntu kernel, please open a new bug against that kernel version and provide the updated details, with a reference link to the original bug.

This action was performed by an automated process maintained by the Ubuntu Kernel Team.

The task "linux-goldfish (Ubuntu Xenial)" has expired because it has had no new comments or updates for more than three years.

If this issue is still present in an Ubuntu LTS kernel still under active support, please reopen the bug and provide updated details. If this issue was reported against an Ubuntu kernel no longer under active support but the issue still exists in a currently supported Ubuntu kernel, please open a new bug against that kernel version and provide the updated details, with a reference link to the original bug.

This action was performed by an automated process maintained by the Ubuntu Kernel Team.

The task "linux-mako (Ubuntu Xenial)" has expired because it has had no new comments or updates for more than three years.

If this issue is still present in an Ubuntu LTS kernel still under active support, please reopen the bug and provide updated details. If this issue was reported against an Ubuntu kernel no longer under active support but the issue still exists in a currently supported Ubuntu kernel, please open a new bug against that kernel version and provide the updated details, with a reference link to the original bug.

This action was performed by an automated process maintained by the Ubuntu Kernel Team.

The task "linux-flo (Ubuntu Yakkety)" has been closed automatically because it was filed against an Ubuntu release that is now end-of-life.

If this issue is still present in a supported Ubuntu kernel, please open a new bug and provide updated details.

This action was performed by an automated process maintained by the Ubuntu Kernel Team.

The task "linux-goldfish (Ubuntu Yakkety)" has been closed automatically because it was filed against an Ubuntu release that is now end-of-life.

If this issue is still present in a supported Ubuntu kernel, please open a new bug and provide updated details.

This action was performed by an automated process maintained by the Ubuntu Kernel Team.

The task "linux-mako (Ubuntu Yakkety)" has been closed automatically because it was filed against an Ubuntu release that is now end-of-life.

If this issue is still present in a supported Ubuntu kernel, please open a new bug and provide updated details.

This action was performed by an automated process maintained by the Ubuntu Kernel Team.