Bug 1450261 (CVE-2017-7495)
Summary: | CVE-2017-7495 kernel: ext4: power failure during write(2) causes on-disk information leak | ||
---|---|---|---|
Product: | [Other] Security Response | Reporter: | Wade Mealing <wmealing> |
Component: | vulnerability | Assignee: | Red Hat Product Security <security-response-team> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | unspecified | CC: | aquini, bhu, dhoward, dominik.mierzejewski, esammons, fhrbata, iboverma, jross, kernel-mgr, lczerner, lwang, matt, mcressma, mguzik, nmurray, pholasek, plougher, pmatouse, rvrbovsk, slawomir, vdronov, williams, wmealing |
Target Milestone: | --- | Keywords: | Security |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: |
A vulnerability was found in the Linux kernel where filesystems mounted with data=ordered mode may allow an attacker to read stale data from recently allocated blocks in new files after a system 'reset' by abusing ext4 mechanics of delayed allocation.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-03-23 15:12:46 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1454551, 1454552, 1454553, 1461806, 1461807 | ||
Bug Blocks: | 1325973 |
Description
Wade Mealing
2017-05-12 03:17:41 UTC
Mitigation: Alternative filesystems may be used in place of ext4 in case of sensitive data leak. Alternatively, don't hard reset the system. Acknowledgments: Name: Takeshi Nishimura (NEC) Statement: This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. Future Linux kernel updates for the respective releases may address this issue. fs |