linux: In the Linux kernel, the following vulnerability has been resolved: mm/hwpoison: clear MF_COUNT_INCREASED before ret...
CVE-2021-47090 is fixed in 24 products on 1 platform, first by RHSA-2022:7683, released November 8, 2022. It is not reported as exploited. Patch Radar priority: Routine.
In the Linux kernel, the following vulnerability has been resolved: mm/hwpoison: clear MF_COUNT_INCREASED before retrying get_any_page() Hulk Robot reported a panic in put_page_testzero() when testing madvise() with MADV_SOFT_OFFLINE. The BUG() is triggered when retrying get_any_page(). This is because we keep MF_COUNT_INCREASED flag in second try but the refcnt is not increased. page dumped because: VM_BUG_ON_PAGE(page_ref_count(page) == 0) ------------[ cut here ]------------ kernel BUG at include/linux/mm.h:737! invalid opcode: 0000 [#1] PREEMPT SMP CPU: 5 PID: 2135 Comm: sshd Tainted: G B 5.16.0-rc6-dirty #373 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 RIP: release_pages+0x53f/0x840 Call Trace: free_pages_and_swap_cache+0x64/0x80 tlb_flush_mmu+0x6f/0x220 unmap_page_range+0xe6c/0x12c0 unmap_single_vma+0x90/0x170 unmap_vmas+0xc4/0x180 exit_mmap+0xde/0x3a0 mmput+0xa3/0x250 do_exit+0x564/0x1470 do_group_exit+0x3b/0x100 __do_sys_exit_group+0x13/0x20 __x64_sys_exit_group+0x16/0x20 do_syscall_64+0x34/0x80 entry_SYSCALL_64_after_hwframe+0x44/0xae Modules linked in: ---[ end trace e99579b570fe0649 ]--- RIP: 0010:release_pages+0x53f/0x840
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| bpftool · RHEL 8 | 0:4.18.0-425.3.1.el8 | RHSA-2022:7683 | Nov 8, 2022 |
| kernel · RHEL 8 | 0:4.18.0-425.3.1.el8 | RHSA-2022:7683 | Nov 8, 2022 |
| kernel-abi-stablelists · RHEL 8 | 0:4.18.0-425.3.1.el8 | RHSA-2022:7683 | Nov 8, 2022 |
| kernel-core · RHEL 8 | 0:4.18.0-425.3.1.el8 | RHSA-2022:7683 | Nov 8, 2022 |
| kernel-debug · RHEL 8 | 0:4.18.0-425.3.1.el8 | RHSA-2022:7683 | Nov 8, 2022 |
| kernel-debug-core · RHEL 8 | 0:4.18.0-425.3.1.el8 | RHSA-2022:7683 | Nov 8, 2022 |
| kernel-debug-devel · RHEL 8 | 0:4.18.0-425.3.1.el8 | RHSA-2022:7683 | Nov 8, 2022 |
| kernel-debug-modules · RHEL 8 | 0:4.18.0-425.3.1.el8 | RHSA-2022:7683 | Nov 8, 2022 |
| kernel-debug-modules-extra · RHEL 8 | 0:4.18.0-425.3.1.el8 | RHSA-2022:7683 | Nov 8, 2022 |
| kernel-devel · RHEL 8 | 0:4.18.0-425.3.1.el8 | RHSA-2022:7683 | Nov 8, 2022 |
| kernel-doc · RHEL 8 | 0:4.18.0-425.3.1.el8 | RHSA-2022:7683 | Nov 8, 2022 |
| kernel-modules · RHEL 8 | 0:4.18.0-425.3.1.el8 | RHSA-2022:7683 | Nov 8, 2022 |
| kernel-modules-extra · RHEL 8 | 0:4.18.0-425.3.1.el8 | RHSA-2022:7683 | Nov 8, 2022 |
| kernel-tools · RHEL 8 | 0:4.18.0-425.3.1.el8 | RHSA-2022:7683 | Nov 8, 2022 |
| kernel-tools-libs · RHEL 8 | 0:4.18.0-425.3.1.el8 | RHSA-2022:7683 | Nov 8, 2022 |
| kernel-tools-libs-devel · RHEL 8 | 0:4.18.0-425.3.1.el8 | RHSA-2022:7683 | Nov 8, 2022 |
| kernel-zfcpdump · RHEL 8 | 0:4.18.0-425.3.1.el8 | RHSA-2022:7683 | Nov 8, 2022 |
| kernel-zfcpdump-core · RHEL 8 | 0:4.18.0-425.3.1.el8 | RHSA-2022:7683 | Nov 8, 2022 |
| kernel-zfcpdump-devel · RHEL 8 | 0:4.18.0-425.3.1.el8 | RHSA-2022:7683 | Nov 8, 2022 |
| kernel-zfcpdump-modules · RHEL 8 | 0:4.18.0-425.3.1.el8 | RHSA-2022:7683 | Nov 8, 2022 |
| kernel-zfcpdump-modules-extra · RHEL 8 | 0:4.18.0-425.3.1.el8 | RHSA-2022:7683 | Nov 8, 2022 |
| linux · Debian 12.15 (bookworm) | 5.15.15-1 | DEBIAN-CVE-2021-47090 | Mar 4, 2024 |
| linux · Debian 13.5 (trixie) | 5.15.15-1 | DEBIAN-CVE-2021-47090 | Mar 4, 2024 |
| linux · Debian 14 | 5.15.15-1 | DEBIAN-CVE-2021-47090 | Mar 4, 2024 |
| perf · RHEL 8 | 0:4.18.0-425.3.1.el8 | RHSA-2022:7683 | Nov 8, 2022 |
| python3-perf · RHEL 8 | 0:4.18.0-425.3.1.el8 | RHSA-2022:7683 | Nov 8, 2022 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.