CVSS: 4.7EPSS: 0%CPEs: 11EXPL: 0CVE-2022-49607 – perf/core: Fix data race between perf_event_set_output() and perf_mmap_close()
https://notcve.org/view.php?id=CVE-2022-49607
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: perf/core: Fix data race between perf_event_set_output() and perf_mmap_close() Yang Jihing reported a race between perf_event_set_output() and perf_mmap_close(): CPU1 CPU2 perf_mmap_close(e2) if (atomic_dec_and_test(&e2->rb->mmap_count)) // 1 - > 0 detach_rest = true ioctl(e1, IOC_SET_OUTPUT, e2) perf_event_set_output(e1, e2) ... list_for_each_entry_rcu(e, &e2->rb->event_list, rb_entry) ring_buffer_attach(e, NULL); // e1 isn't yet added and... • https://git.kernel.org/stable/c/9bb5d40cd93c9dd4be74834b1dcb1ba03629716b •
CVSS: 6.6EPSS: 0%CPEs: 3EXPL: 0CVE-2022-49606 – RDMA/irdma: Fix sleep from invalid context BUG
https://notcve.org/view.php?id=CVE-2022-49606
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: RDMA/irdma: Fix sleep from invalid context BUG Taking the qos_mutex to process RoCEv2 QP's on netdev events causes a kernel splat. Fix this by removing the handling for RoCEv2 in irdma_cm_teardown_connections that uses the mutex. This handling is only needed for iWARP to avoid having connections established while the link is down or having connections remain functional after the IP address is removed. BUG: sleeping function called from inva... • https://git.kernel.org/stable/c/146b9756f14c04894226fb97e2f102f217139c27 •
CVSS: 5.5EPSS: 0%CPEs: 5EXPL: 0CVE-2022-49605 – igc: Reinstate IGC_REMOVED logic and implement it properly
https://notcve.org/view.php?id=CVE-2022-49605
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: igc: Reinstate IGC_REMOVED logic and implement it properly The initially merged version of the igc driver code (via commit 146740f9abc4, "igc: Add support for PF") contained the following IGC_REMOVED checks in the igc_rd32/wr32() MMIO accessors: u32 igc_rd32(struct igc_hw *hw, u32 reg) { u8 __iomem *hw_addr = READ_ONCE(hw->hw_addr); u32 value = 0; if (IGC_REMOVED(hw_addr)) return ~value; value = readl(&hw_addr[reg]); /* reads should not ret... • https://git.kernel.org/stable/c/146740f9abc4976e4f0af1aa302efee1c699d2e4 •
CVSS: 5.5EPSS: 0%CPEs: 6EXPL: 0CVE-2022-49604 – ip: Fix data-races around sysctl_ip_fwd_use_pmtu.
https://notcve.org/view.php?id=CVE-2022-49604
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: ip: Fix data-races around sysctl_ip_fwd_use_pmtu. While reading sysctl_ip_fwd_use_pmtu, it can be changed concurrently. Thus, we need to add READ_ONCE() to its readers. In the Linux kernel, the following vulnerability has been resolved: ip: Fix data-races around sysctl_ip_fwd_use_pmtu. While reading sysctl_ip_fwd_use_pmtu, it can be changed concurrently. Thus, we need to add READ_ONCE() to its readers. • https://git.kernel.org/stable/c/f87c10a8aa1e82498c42d0335524d6ae7cf5a52b •
CVSS: 5.5EPSS: 0%CPEs: 4EXPL: 0CVE-2022-49603 – ip: Fix data-races around sysctl_ip_fwd_update_priority.
https://notcve.org/view.php?id=CVE-2022-49603
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: ip: Fix data-races around sysctl_ip_fwd_update_priority. While reading sysctl_ip_fwd_update_priority, it can be changed concurrently. Thus, we need to add READ_ONCE() to its readers. In the Linux kernel, the following vulnerability has been resolved: ip: Fix data-races around sysctl_ip_fwd_update_priority. While reading sysctl_ip_fwd_update_priority, it can be changed concurrently. • https://git.kernel.org/stable/c/432e05d328921c68c35bfdeff7d7b7400b8e3d1a •
CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0CVE-2022-49602 – ip: Fix a data-race around sysctl_fwmark_reflect.
https://notcve.org/view.php?id=CVE-2022-49602
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: ip: Fix a data-race around sysctl_fwmark_reflect. While reading sysctl_fwmark_reflect, it can be changed concurrently. Thus, we need to add READ_ONCE() to its reader. In the Linux kernel, the following vulnerability has been resolved: ip: Fix a data-race around sysctl_fwmark_reflect. While reading sysctl_fwmark_reflect, it can be changed concurrently. Thus, we need to add READ_ONCE() to its reader. • https://git.kernel.org/stable/c/e110861f86094cd78cc85593b873970092deb43a •
CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0CVE-2022-49601 – tcp/dccp: Fix a data-race around sysctl_tcp_fwmark_accept.
https://notcve.org/view.php?id=CVE-2022-49601
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: tcp/dccp: Fix a data-race around sysctl_tcp_fwmark_accept. While reading sysctl_tcp_fwmark_accept, it can be changed concurrently. Thus, we need to add READ_ONCE() to its reader. In the Linux kernel, the following vulnerability has been resolved: tcp/dccp: Fix a data-race around sysctl_tcp_fwmark_accept. While reading sysctl_tcp_fwmark_accept, it can be changed concurrently. Thus, we need to add READ_ONCE() to its reader. • https://git.kernel.org/stable/c/84f39b08d7868ce10eeaf640627cb89777f0ae93 •
CVSS: 5.5EPSS: 0%CPEs: 4EXPL: 0CVE-2022-49600 – ip: Fix a data-race around sysctl_ip_autobind_reuse.
https://notcve.org/view.php?id=CVE-2022-49600
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: ip: Fix a data-race around sysctl_ip_autobind_reuse. While reading sysctl_ip_autobind_reuse, it can be changed concurrently. Thus, we need to add READ_ONCE() to its reader. In the Linux kernel, the following vulnerability has been resolved: ip: Fix a data-race around sysctl_ip_autobind_reuse. While reading sysctl_ip_autobind_reuse, it can be changed concurrently. Thus, we need to add READ_ONCE() to its reader. • https://git.kernel.org/stable/c/4b01a9674231a97553a55456d883f584e948a78d •
CVSS: 5.5EPSS: 0%CPEs: 4EXPL: 0CVE-2022-49599 – tcp: Fix data-races around sysctl_tcp_l3mdev_accept.
https://notcve.org/view.php?id=CVE-2022-49599
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: tcp: Fix data-races around sysctl_tcp_l3mdev_accept. While reading sysctl_tcp_l3mdev_accept, it can be changed concurrently. Thus, we need to add READ_ONCE() to its readers. In the Linux kernel, the following vulnerability has been resolved: tcp: Fix data-races around sysctl_tcp_l3mdev_accept. While reading sysctl_tcp_l3mdev_accept, it can be changed concurrently. Thus, we need to add READ_ONCE() to its readers. • https://git.kernel.org/stable/c/6dd9a14e92e54895e143f10fef4d0b9abe109aa9 •
CVSS: 5.5EPSS: 0%CPEs: 6EXPL: 0CVE-2022-49598 – tcp: Fix data-races around sysctl_tcp_mtu_probing.
https://notcve.org/view.php?id=CVE-2022-49598
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: tcp: Fix data-races around sysctl_tcp_mtu_probing. While reading sysctl_tcp_mtu_probing, it can be changed concurrently. Thus, we need to add READ_ONCE() to its readers. In the Linux kernel, the following vulnerability has been resolved: tcp: Fix data-races around sysctl_tcp_mtu_probing. While reading sysctl_tcp_mtu_probing, it can be changed concurrently. Thus, we need to add READ_ONCE() to its readers. • https://git.kernel.org/stable/c/5d424d5a674f782d0659a3b66d951f412901faee •