In the Linux kernel, the following vulnerability has been resolved: mm/memory-failure: make sure wait for page writeback in memory_failure The Linux kernel CVE team has assigned CVE-2021-47256 to this issue. Upstream advisory: https://lore.kernel.org/linux-cve-announce/2024052146-CVE-2021-47256-a490@gregkh/T
The result of automatic check (that is developed by Alexander Larkin) for this CVE-2021-47256 is: CHECK Maybe valid. Check manually. with impact MODERATE (that is an approximation based on flags READ DANGER DISK ; these flags parsed automatically based on patch data). Such automatic check happens only for Low/Moderates (and only when not from reporter, but parsing already existing CVE). Highs always checked manually (I check it myself and then we check it again in Remediation team). In rare cases some of the Moderates could be increased to High later.
Hey @Alex I see that the reported already checked and noticed this fix is in RHEL 8: $ kerneloscope downstream e8675d291ac0 944bd962177f (in rhel-8.5, rhel-8.6, rhel-8.7, rhel-8.8, rhel-8.9, rhel-8.10) mm/memory-failure: make sure wait for page writeback in memory_failure Can you give me some insight into why we still opened trackers for this issue and what I am supposed to do with these trackers? Thanks
In reply to comment #11: > Hey @Alex > > I see that the reported already checked and noticed this fix is in RHEL 8: > > $ kerneloscope downstream e8675d291ac0 > 944bd962177f (in rhel-8.5, rhel-8.6, rhel-8.7, rhel-8.8, rhel-8.9, > rhel-8.10) mm/memory-failure: make sure wait for page writeback in > memory_failure > > Can you give me some insight into why we still opened trackers for this > issue and what I am supposed to do with these trackers? > > Thanks Just close it. Starting from July all trackers created by default for all-streams (including Z-stream trackers) without prior manual check if affected or not. I closed rhel8 trackers.