Bug 1610102 (CVE-2018-14615)
| Summary: | CVE-2018-14615 kernel: Buffer overflow in fs/f2fs/inline.c:truncate_inline_inode() when unmounting a crafted f2fs image | ||
|---|---|---|---|
| Product: | [Other] Security Response | Reporter: | Sam Fowler <sfowler> |
| Component: | vulnerability | Assignee: | Red Hat Product Security <security-response-team> |
| Status: | CLOSED NOTABUG | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | unspecified | CC: | abhgupta, airlied, aquini, bhu, blc, bskeggs, dbaker, dhoward, esammons, ewk, fhrbata, hdegoede, hkrzesin, hwkernel-mgr, iboverma, ichavero, itamar, jarodwilson, jforbes, jglisse, jkacur, john.j5live, jokerman, jonathan, josef, jross, jwboyer, kernel-maint, kernel-mgr, labbott, lgoncalv, linville, lwang, matt, mchehab, mcressma, mguzik, mjg59, mlangsdo, nmurray, plougher, rt-maint, rvrbovsk, skozina, slawomir, steved, sthangav, trankin, vdronov, williams |
| Target Milestone: | --- | Keywords: | Security |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: |
An issue was discovered in the Linux kernel's F2FS filesystem code. A buffer overflow in truncate_inline_inode() in the fs/f2fs/inline.c function, when umounting a crafted f2fs image, can occur because a length value may be negative.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-08-02 16:42:16 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: | 1610103, 1610104 | ||
| Bug Blocks: | 1610105 | ||
|
Description
Sam Fowler
2018-07-31 01:47:52 UTC
Created kernel tracking bugs for this issue: Affects: fedora-all [bug 1610103] Note: An F2FS filesystem is not shipped with any of the Red Hat products. This is fixed for Fedora with the 4.18 rebases. |