Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 547255 - (CVE-2009-4308) CVE-2009-4308 kernel: ext4: Avoid null pointer dereference when decoding EROFS w/o a journal
CVE-2009-4308 kernel: ext4: Avoid null pointer dereference when decoding EROF...
Status: CLOSED ERRATA
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,reported=20091214,pub...
: Security
Depends On: 547256 547257
Blocks:
  Show dependency treegraph
 
Reported: 2009-12-14 00:56 EST by Eugene Teo (Security Response)
Modified: 2015-07-29 13:47 EDT (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-07-10 12:20:31 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)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2010:0147 normal SHIPPED_LIVE Important: kernel security and bug fix update 2010-03-16 20:18:44 EDT

  None (edit)
Description Eugene Teo (Security Response) 2009-12-14 00:56:16 EST
Description of problem:
ext4: Avoid null pointer dereference when decoding EROFS w/o a journal
    
We need to check to make sure a journal is present before checking the journal flags in ext4_decode_error().

Upstream commit:
http://git.kernel.org/linus/78f1ddbb498283c2445c11b0dfa666424c301803

Reference:
http://secunia.com/advisories/37658
Comment 3 Aristeu Rozanski 2010-01-26 08:40:24 EST
Patch present on the current RHEL6 git tree
Comment 4 errata-xmlrpc 2010-03-16 20:19:07 EDT
This issue has been addressed in following products:

  Red Hat Enterprise Linux 5

Via RHSA-2010:0147 https://rhn.redhat.com/errata/RHSA-2010-0147.html

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