Bug 1205079 (CVE-2014-9710) - CVE-2014-9710 Kernel: fs: btrfs: non-atomic xattr replace operation
Summary: CVE-2014-9710 Kernel: fs: btrfs: non-atomic xattr replace operation
Alias: CVE-2014-9710
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1205084 1205085 1205086 1205087 1205088 1205873
Blocks: 1161399
TreeView+ depends on / blocked
Reported: 2015-03-24 08:25 UTC by Prasad Pandit
Modified: 2023-10-06 17:28 UTC (History)
25 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2019-06-08 02:40:29 UTC

Attachments (Terms of Use)

Description Prasad Pandit 2015-03-24 08:25:48 UTC
Linux kernel built with the Btrfs Filesystem support(CONFIG_BTRFS_FS) is
vulnerable to a race condition which leaves the extended attribute(xattr)
empty for a short time window. This could be leveraged to bypass set ACLs
and potentially escalate user privileges.

An unprivileged user could use this flaw to potentially escalate privileges on
a system.

Upstream fix:
  -> https://git.kernel.org/linus/5f5bc6b1e2d5a6f827bc860ef2dc5b6f365d1339

Comment 1 Prasad Pandit 2015-03-24 08:28:53 UTC

This issue does not affect the versions of the kernel package as shipped with
Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG 2.

This issue affects the version of Linux kernel as shipped with Red Hat Enterprise Linux 6 and 7. Future kernel updates for Red Hat Enterprise Linux 7 may address this issue.

Given the Moderate impact and the fact that BRTFS file system is no longer Technology preview in Red Hat Enterprise Linux 6 this issue is not currently planned to be addressed in future releases of Red Hat Enterprise Linux 6.

Comment 3 Prasad Pandit 2015-03-24 08:36:24 UTC
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 1205088]

Comment 4 Prasad Pandit 2015-03-27 08:13:16 UTC

This issue was discovered by Alexandre Oliva of Red Hat Inc.

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