1115 matches found
CVE-2022-49580
The CVE-2022-49580 entry describes a data-race in the Linux kernel IPv4 path around reading sysctl_fib_multipath_use_neigh, which could be changed concurrently. The referenced fix adds READ_ONCE() to the reader to guard against concurrent modification. Affected software is the Linux kernel (IPv4 ...
CVE-2022-49578 ip: Fix data-races around sysctl_ip_prot_sock.
In the Linux kernel, the following vulnerability has been resolved: ip: Fix data-races around sysctlipprotsock. sysctlipprotsock 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...
CVE-2022-49578
CVE-2022-49578 concerns a data race in the Linux kernel related to sysctl_ip_prot_sock. The root cause is concurrent access to sysctl_ip_prot_sock, causing load/store tearing unless proper synchronization is used. The vulnerability affects the kernel’s IP/sysctl handling and is stated as resolved...
CVE-2022-49576 ipv4: Fix data-races around sysctl_fib_multipath_hash_fields.
In the Linux kernel, the following vulnerability has been resolved: ipv4: Fix data-races around sysctlfibmultipathhashfields. While reading sysctlfibmultipathhashfields, it can be changed concurrently. Thus, we need to add READONCE to its readers...
CVE-2022-49576
In the Linux kernel, the following vulnerability has been resolved: ipv4: Fix data-races around sysctlfibmultipathhashfields. While reading sysctlfibmultipathhashfields, it can be changed concurrently. Thus, we need to add READONCE to its readers...
CVE-2022-49576 ipv4: Fix data-races around sysctl_fib_multipath_hash_fields.
In the Linux kernel, the following vulnerability has been resolved: ipv4: Fix data-races around sysctlfibmultipathhashfields. While reading sysctlfibmultipathhashfields, it can be changed concurrently. Thus, we need to add READONCE to its readers...
CVE-2022-49575 tcp: Fix a data-race around sysctl_tcp_thin_linear_timeouts.
In the Linux kernel, the following vulnerability has been resolved: tcp: Fix a data-race around sysctltcpthinlineartimeouts. While reading sysctltcpthinlineartimeouts, it can be changed concurrently. Thus, we need to add READONCE to its reader...
CVE-2022-49575 tcp: Fix a data-race around sysctl_tcp_thin_linear_timeouts.
In the Linux kernel, the following vulnerability has been resolved: tcp: Fix a data-race around sysctltcpthinlineartimeouts. While reading sysctltcpthinlineartimeouts, it can be changed concurrently. Thus, we need to add READONCE to its reader...
CVE-2022-49575
CVE-2022-49575: Linux kernel patch fixes a data race in the reader of sysctl_tcp_thin_linear_timeouts by adding READ_ONCE(). The vulnerability arises from concurrent reads/writes to that sysctl during access. Impact is listed as Availability impact (HIGH) with Local attack vector and HIGH complex...
CVE-2022-49574 tcp: Fix data-races around sysctl_tcp_recovery.
In the Linux kernel, the following vulnerability has been resolved: tcp: Fix data-races around sysctltcprecovery. While reading sysctltcprecovery, it can be changed concurrently. Thus, we need to add READONCE to its readers...
CVE-2022-49573 tcp: Fix a data-race around sysctl_tcp_early_retrans.
In the Linux kernel, the following vulnerability has been resolved: tcp: Fix a data-race around sysctltcpearlyretrans. While reading sysctltcpearlyretrans, it can be changed concurrently. Thus, we need to add READONCE to its reader...
CVE-2022-49574 tcp: Fix data-races around sysctl_tcp_recovery.
In the Linux kernel, the following vulnerability has been resolved: tcp: Fix data-races around sysctltcprecovery. While reading sysctltcprecovery, it can be changed concurrently. Thus, we need to add READONCE to its readers...
CVE-2022-49574
CVE-2022-49574 is a Linux kernel security issue involving a data race in reading the sysctl_tcp_recovery variable within the TCP stack. The root cause is concurrent modification of sysctl_tcp_recovery while it is being read, which could lead to inconsistent reads or memory corruption. The descrip...
CVE-2022-49573 tcp: Fix a data-race around sysctl_tcp_early_retrans.
In the Linux kernel, the following vulnerability has been resolved: tcp: Fix a data-race around sysctltcpearlyretrans. While reading sysctltcpearlyretrans, it can be changed concurrently. Thus, we need to add READONCE to its reader...
CVE-2022-49574 tcp: Fix data-races around sysctl_tcp_recovery.
In the Linux kernel, the following vulnerability has been resolved: tcp: Fix data-races around sysctltcprecovery. While reading sysctltcprecovery, it can be changed concurrently. Thus, we need to add READONCE to its readers...
CVE-2022-49572
CVE-2022-49572 affects the Linux kernel tcp path. The issue is a data race around reading the sysctl_tcp_slow_start_after_idle variable, where reads could race with concurrent writes. The published fix adds a READ_ONCE() to the readers to prevent concurrent modification during reads. The vulnerab...
CVE-2022-49572 tcp: Fix data-races around sysctl_tcp_slow_start_after_idle.
In the Linux kernel, the following vulnerability has been resolved: tcp: Fix data-races around sysctltcpslowstartafteridle. While reading sysctltcpslowstartafteridle, it can be changed concurrently. Thus, we need to add READONCE to its readers...
CVE-2022-49572 tcp: Fix data-races around sysctl_tcp_slow_start_after_idle.
In the Linux kernel, the following vulnerability has been resolved: tcp: Fix data-races around sysctltcpslowstartafteridle. While reading sysctltcpslowstartafteridle, it can be changed concurrently. Thus, we need to add READONCE to its readers...
CVE-2022-49572
In the Linux kernel, the following vulnerability has been resolved: tcp: Fix data-races around sysctltcpslowstartafteridle. While reading sysctltcpslowstartafteridle, it can be changed concurrently. Thus, we need to add READONCE to its readers...
CVE-2022-49571 tcp: Fix data-races around sysctl_tcp_max_reordering.
In the Linux kernel, the following vulnerability has been resolved: tcp: Fix data-races around sysctltcpmaxreordering. While reading sysctltcpmaxreordering, it can be changed concurrently. Thus, we need to add READONCE to its readers...