What | Removed | Added |
---|---|---|
Status | IN_PROGRESS | RESOLVED |
CC | astieger@suse.com | |
Component | Security | Other |
Resolution | --- | UPSTREAM |
Summary | VUL-1: R-base: possible memory leak | R-base: possible memory leak |
Severity | Normal | Minor |
(In reply to Detlef Steuer from comment #1) > R-3.1.1 is really old. > > Factory now contains R-3.2.0. Now 3.2.1. > Does it still exist? Victor could you please re-run with Factory, or share generic instructions to maintainer so he could re-run? > And: I must admit I have no idea what to do besides telling upstream, if it > still exists in R-3.2.0 Detlef if you could attempt to reproduce the memory leak with ASAN and tell upstream that would be nice. That being said, resolving as "upstream" what looks like a simple memory handling bug, unless we find a reason why this would be exploitable and significant enough to be security relevant.