Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1597814 - (CVE-2018-13100) CVE-2018-13100 kernel: divide-by-zero in fs/f2fs/super.c
CVE-2018-13100 kernel: divide-by-zero in fs/f2fs/super.c
Status: CLOSED NOTABUG
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20180622,reported=2...
: Security
Depends On: 1597816 1597819
Blocks: 1597817
  Show dependency treegraph
 
Reported: 2018-07-03 12:30 EDT by Laura Pardo
Modified: 2018-09-11 16:56 EDT (History)
47 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
An issue was discovered in fs/f2fs/super.c in the Linux kernel, which does not properly validate secs_per_zone in a corrupted f2fs image. This may lead to a divide-by-zero error and a system crash.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-07-10 07:50:05 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Laura Pardo 2018-07-03 12:30:43 EDT
An issue was discovered in fs/f2fs/super.c in the Linux kernel, which does not properly validate secs_per_zone in a corrupted f2fs image, which may lead to a divide-by-zero error and a system crash.

References:

https://bugzilla.kernel.org/show_bug.cgi?id=200183 	

A suggested upstream patch:

https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git/commit/?h=f2fs-dev&id=977f9bb558cb4a95d53b10301f5c739ed8867d4d
Comment 1 Laura Pardo 2018-07-03 12:32:21 EDT
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 1597816]
Comment 6 Vladis Dronov 2018-07-10 07:50:05 EDT
Note:

An F2FS filesystem is not shipped with any of the Red Hat products.
Comment 7 Justin M. Forbes 2018-09-11 16:56:43 EDT
This issue is fixed for Fedora with the 4.18 rebases.

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