| Summary: | kernel: Kernel panic when mounting specially crafted ext2 filesystem | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Other] Security Response | Reporter: | Adam Mariš <amaris> | ||||
| Component: | vulnerability | Assignee: | Red Hat Product Security <security-response-team> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | |||||
| Severity: | low | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | unspecified | CC: | agordeev, anemec, aquini, bhu, dhoward, esammons, fhrbata, iboverma, jkacur, joelsmith, jross, kernel-mgr, kstutsma, lgoncalv, lwang, matt, mcressma, mguzik, nmurray, pholasek, plougher, rvrbovsk, security-response-team, slawomir, vdronov, williams | ||||
| Target Milestone: | --- | Keywords: | Security | ||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-05-28 15:15: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: | 1322277 | ||||||
| Bug Blocks: | 1313817 | ||||||
| Attachments: |
|
||||||
|
Description
Adam Mariš
2016-03-02 11:59:00 UTC
Acknowledgments: Name: Hugues Anguelkov Created attachment 1132278 [details]
Crash report
Created kernel tracking bugs for this issue: Affects: fedora-all [bug 1322277] Public via: http://seclists.org/oss-sec/2016/q1/709 Upstream's stance on this bug: http://marc.info/?l=linux-ext4&m=145937069606704&w=2 Basically, they plan on doing nothing in the kernel. The two suggestions of running fsck and mounting with -o errors=continue are feasible, but they would need to be done in userspace. Statement: This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2. This has been rated as having Low security impact, as this is actually not a security flaw but intended kernel reaction. This is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. |