Bug 748695 - CVE-2011-1833 kernel: ecryptfs: mount source TOCTOU race [fedora-all]
CVE-2011-1833 kernel: ecryptfs: mount source TOCTOU race [fedora-all]
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
: Security, SecurityTracking
Depends On:
Blocks: CVE-2011-1833
  Show dependency treegraph
Reported: 2011-10-25 00:09 EDT by Eugene Teo (Security Response)
Modified: 2011-10-25 09:11 EDT (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Release Note
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-10-25 09:11:29 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Eugene Teo (Security Response) 2011-10-25 00:09:33 EDT
This is an automatically created tracking bug!  It was created to ensure
that one or more security vulnerabilities are fixed in affected Fedora

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

For more information see:

When creating a Bodhi update request, please include the bug IDs of the
respective parent bugs filed against the "Security Response" product.
Please mention CVE ids in the RPM changelog when available.

Bodhi update submission link:

Please note: this issue affects multiple supported versions of Fedora.
Only one tracking bug has been filed; please only close it when all
affected versions are fixed.

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 Josh Boyer 2011-10-25 09:11:29 EDT
Fixed in 3.1 upstream.

F16/rawhide contains 3.1, so fixed there.
F15 contains the fix as it was included in the 3.0.2 stable release.
F14 contains a backported patch to fix this in the release.

Note You need to log in before you can comment on or make changes to this bug.