|
Bugzilla – Full Text Bug Listing |
| Summary: | VUL-0: REJECTED: CVE-2021-47543: kernel: perf report: Fix memory leaks around perf_tip() | ||
|---|---|---|---|
| Product: | [Novell Products] SUSE Security Incidents | Reporter: | SMASH SMASH <smash_bz> |
| Component: | Incidents | Assignee: | Security Team bot <security-team> |
| Status: | RESOLVED INVALID | QA Contact: | Security Team bot <security-team> |
| Severity: | Normal | ||
| Priority: | P3 - Medium | CC: | andrea.mattiazzo, jlee, mhocko, security-team |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| URL: | https://smash.suse.de/issue/407703/ | ||
| Whiteboard: | CVSSv3.1:SUSE:CVE-2021-47543:3.3:(AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L) | ||
| Found By: | Security Response Team | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
SMASH SMASH
2024-05-28 09:22:05 UTC
Based on the fixing commit (d9fc706108c15f8bc2d4ccccf8e50f74830fabd9) this is a userspace leak (tools/perf). Which can occur when running 'perf report' which has a generally short lived lifespan. How on earth did this get a CVE assigned? From 2021? I really don't see that this is anything we need to be concerned with. Also due to the high level of code churn in perf userspace, backports are more challenging than for the kernel code. CVE is now rejected. https://lore.kernel.org/linux-cve-announce/2024061337-delegator-chafe-bf6d@gregkh/ Thanks all. Closing. |