Bug 1368919

Summary:	CVE-2015-8952 kernel: mbcache code subject to softlockup DOS in cache management [fedora-all]
Product:	[Fedora] Fedora	Reporter:	Prasad Pandit <ppandit>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	24	CC:	gansalmon, ichavero, itamar, jforbes, jonathan, jwboyer, kernel-maint, labbott, madhu.chinakonda, mchehab, ppandit
Target Milestone:	---	Keywords:	Security, SecurityTracking
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Release Note
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-10-04 16:25:04 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	1360968

Description Prasad Pandit 2016-08-22 06:35:11 UTC

This is an automatically created tracking bug!  It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora.

For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.

For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs

When submitting as an update, use the fedpkg template provided in the next
comment(s).  This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.

Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.

NOTE: this issue affects multiple supported versions of Fedora. While only
one tracking bug has been filed, please correct all affected versions at
the same time.  If you need to fix the versions independent of each other,
you may clone this bug as appropriate.

Reproducers, if any, will remain confidential and never be made public, unless done so by the security team.

[bug automatically created by: add-tracking-bugs]

Comment 1 Prasad Pandit 2016-08-22 06:35:25 UTC

Use the following template to for the 'fedpkg update' request to submit an
update for this issue as it contains the top-level parent bug(s) as well as
this tracking bug.  This will ensure that all associated bugs get updated
when new packages are pushed to stable.

=====

# bugfix, security, enhancement, newpackage (required)
type=security

# testing, stable
request=testing

# Bug numbers: 1234,9876
bugs=1360968,1368919

# Description of your update
notes=Security fix for 

# Enable request automation based on the stable/unstable karma thresholds
autokarma=True
stable_karma=3
unstable_karma=-3

# Automatically close bugs when this marked as stable
close_bugs=True

# Suggest that users restart after update
suggest_reboot=False

======

Additionally, you may opt to use the bodhi web interface to submit updates:

https://bodhi.fedoraproject.org/updates/new

Comment 2 Laura Abbott 2016-09-23 19:09:13 UTC

*********** MASS BUG UPDATE **************
 
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 24 kernel bugs.
 
Fedora 24 has now been rebased to 4.7.4-200.fc24.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 25, and are still experiencing this issue, please change the version to Fedora 25.
 
If you experience different issues, please open a new bug report for those.

Comment 3 Prasad Pandit 2016-10-04 16:24:22 UTC

(In reply to Laura Abbott from comment #2)
> Fedora 24 has now been rebased to 4.7.4-200.fc24.  Please test this kernel
> update (or newer) and let us know if you issue has been resolved or if it is
> still present with the newer kernel.

  I tried the reproducer on F23 kernel-4.7.3-100.fc23.x86_64, which includes the series of upstream commits which fix this issue.

  -> https://bugzilla.kernel.org/show_bug.cgi?id=107301#c27

  f9a61eb4e2471c56a63cd804c7474128138c38ac
  82939d7999dfc1f1998c4b1c12e2f19edbdff272
  be0726d33cb8f411945884664924bed3cb8c70ee
  ecd1e64412d5242b8afdef58a714bab3c5464f79
  c2f3140fe2eceb3a6c1615b2648b9471544881c6
  f0c8b46238db9d51ef9ea0858259958d0c601cec
  7a2508e1b657cfc7e1371550f88c7a7bc4288f32
  2335d05f3a83f5290ec28c1ed30c1c742a37edc9
  dc8d5e565f00c9442fa1cbf9acc115475628527c
  3fd164629d25b04f291a79a013dcc7ce1a301269
  6048c64b26097a0ffbd966866b599f990e674e9b

It did not reproduce the soft lockup issue. This bug can be closed as the 4.7 kernel includes these upstream patches. If the issue crops up again, we'll open another bug.