CVSS: 5.5EPSS: %CPEs: 8EXPL: 0CVE-2022-49587 – tcp: Fix a data-race around sysctl_tcp_notsent_lowat.
https://notcve.org/view.php?id=CVE-2022-49587
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: tcp: Fix a data-race around sysctl_tcp_notsent_lowat. While reading sysctl_tcp_notsent_lowat, 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: Fix a data-race around sysctl_tcp_notsent_lowat. While reading sysctl_tcp_notsent_lowat, it can be changed concurrently. Thus, we need to add READ_ONCE() to its reader. • https://git.kernel.org/stable/c/c9bee3b7fdecb0c1d070c7b54113b3bdfb9a3d36 •
CVSS: 7.1EPSS: %CPEs: 6EXPL: 0CVE-2022-49586 – tcp: Fix data-races around sysctl_tcp_fastopen.
https://notcve.org/view.php?id=CVE-2022-49586
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: tcp: Fix data-races around sysctl_tcp_fastopen. While reading sysctl_tcp_fastopen, 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_fastopen. While reading sysctl_tcp_fastopen, it can be changed concurrently. Thus, we need to add READ_ONCE() to its readers. • https://git.kernel.org/stable/c/2100c8d2d9db23c0a09901a782bb4e3b21bee298 •
CVSS: 5.5EPSS: %CPEs: 4EXPL: 0CVE-2022-49585 – tcp: Fix data-races around sysctl_tcp_fastopen_blackhole_timeout.
https://notcve.org/view.php?id=CVE-2022-49585
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: tcp: Fix data-races around sysctl_tcp_fastopen_blackhole_timeout. While reading sysctl_tcp_fastopen_blackhole_timeout, 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_fastopen_blackhole_timeout. While reading sysctl_tcp_fastopen_blackhole_timeout, it can be changed concurrently. • https://git.kernel.org/stable/c/cf1ef3f0719b4dcb74810ed507e2a2540f9811b4 •
CVSS: 5.5EPSS: %CPEs: 5EXPL: 0CVE-2022-49584 – ixgbe: Add locking to prevent panic when setting sriov_numvfs to zero
https://notcve.org/view.php?id=CVE-2022-49584
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: ixgbe: Add locking to prevent panic when setting sriov_numvfs to zero It is possible to disable VFs while the PF driver is processing requests from the VF driver. This can result in a panic. BUG: unable to handle kernel paging request at 000000000000106c PGD 0 P4D 0 Oops: 0000 [#1] SMP NOPTI CPU: 8 PID: 0 Comm: swapper/8 Kdump: loaded Tainted: G I --------- - Hardware name: Dell Inc. PowerEdge R740/06WXJT, BIOS 2.8.2 08/27/2020 RIP: 0010:ix... • https://git.kernel.org/stable/c/d773d1310625be3b040b436178ad59a0af8888f1 •
CVSS: 7.8EPSS: %CPEs: 8EXPL: 0CVE-2022-49581 – be2net: Fix buffer overflow in be_get_module_eeprom
https://notcve.org/view.php?id=CVE-2022-49581
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: be2net: Fix buffer overflow in be_get_module_eeprom be_cmd_read_port_transceiver_data assumes that it is given a buffer that is at least PAGE_DATA_LEN long, or twice that if the module supports SFF 8472. However, this is not always the case. Fix this by passing the desired offset and length to be_cmd_read_port_transceiver_data so that we only copy the bytes once. In the Linux kernel, the following vulnerability has been resolved: be2net: Fi... • https://git.kernel.org/stable/c/e36edd9d26cf257511548edaf2b7a56eb4fed854 •
CVSS: 5.5EPSS: %CPEs: 5EXPL: 0CVE-2022-49580 – ipv4: Fix a data-race around sysctl_fib_multipath_use_neigh.
https://notcve.org/view.php?id=CVE-2022-49580
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: ipv4: Fix a data-race around sysctl_fib_multipath_use_neigh. While reading sysctl_fib_multipath_use_neigh, 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: ipv4: Fix a data-race around sysctl_fib_multipath_use_neigh. While reading sysctl_fib_multipath_use_neigh, it can be changed concurrently. • https://git.kernel.org/stable/c/a6db4494d218c2e559173661ee972e048dc04fdd •
CVSS: 7.1EPSS: %CPEs: 3EXPL: 0CVE-2022-49579 – ipv4: Fix data-races around sysctl_fib_multipath_hash_policy.
https://notcve.org/view.php?id=CVE-2022-49579
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: ipv4: Fix data-races around sysctl_fib_multipath_hash_policy. While reading sysctl_fib_multipath_hash_policy, 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: ipv4: Fix data-races around sysctl_fib_multipath_hash_policy. While reading sysctl_fib_multipath_hash_policy, it can be changed concurrently. • https://git.kernel.org/stable/c/bf4e0a3db97eb882368fd82980b3b1fa0b5b9778 •
CVSS: 5.5EPSS: %CPEs: 4EXPL: 0CVE-2022-49578 – ip: Fix data-races around sysctl_ip_prot_sock.
https://notcve.org/view.php?id=CVE-2022-49578
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: ip: Fix data-races around sysctl_ip_prot_sock. sysctl_ip_prot_sock is accessed concurrently, and there is always a chance of data-race. So, all readers and writers need some basic protection to avoid load/store-tearing. In the Linux kernel, the following vulnerability has been resolved: ip: Fix data-races around sysctl_ip_prot_sock. sysctl_ip_prot_sock is accessed concurrently, and there is always a chance of data-race. So, all readers and ... • https://git.kernel.org/stable/c/4548b683b78137f8eadeb312b94e20bb0d4a7141 •
CVSS: 5.5EPSS: %CPEs: 5EXPL: 0CVE-2022-49577 – udp: Fix a data-race around sysctl_udp_l3mdev_accept.
https://notcve.org/view.php?id=CVE-2022-49577
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: udp: Fix a data-race around sysctl_udp_l3mdev_accept. While reading sysctl_udp_l3mdev_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: udp: Fix a data-race around sysctl_udp_l3mdev_accept. While reading sysctl_udp_l3mdev_accept, it can be changed concurrently. Thus, we need to add READ_ONCE() to its reader. • https://git.kernel.org/stable/c/63a6fff353d01da5a22b72670c434bf12fa0e3b8 •
CVSS: 5.5EPSS: %CPEs: 6EXPL: 0CVE-2022-49575 – tcp: Fix a data-race around sysctl_tcp_thin_linear_timeouts.
https://notcve.org/view.php?id=CVE-2022-49575
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: tcp: Fix a data-race around sysctl_tcp_thin_linear_timeouts. While reading sysctl_tcp_thin_linear_timeouts, 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: Fix a data-race around sysctl_tcp_thin_linear_timeouts. While reading sysctl_tcp_thin_linear_timeouts, it can be changed concurrently. • https://git.kernel.org/stable/c/36e31b0af58728071e8023cf8e20c5166b700717 •