CVE-2022-49589 igmp: Fix data-races around sysctl_igmp_qrv.

In the Linux kernel, the following vulnerability has been resolved: igmp: Fix data-races around sysctligmpqrv. While reading sysctligmpqrv, it can be changed concurrently. Thus, we need to add READONCE to its readers. This test can be packed into a helper, so such changes will be in the follow-up...

CVE-2022-49589

CVE-2022-49589 affects the Linux kernel igmp subsystem: a data race occurs while reading sysctl_igmp_qrv, since the value could be changed concurrently. The fix described in the description is to add READ_ONCE() to readers of net->ipv4.sysctl_igmp_qrv, with follow-up changes planned after net ...

CVE-2022-49589

In the Linux kernel, the following vulnerability has been resolved: igmp: Fix data-races around sysctligmpqrv. While reading sysctligmpqrv, it can be changed concurrently. Thus, we need to add READONCE to its readers. This test can be packed into a helper, so such changes will be in the follow-up...

CVE-2022-49588 tcp: Fix data-races around sysctl_tcp_migrate_req.

In the Linux kernel, the following vulnerability has been resolved: tcp: Fix data-races around sysctltcpmigratereq. While reading sysctltcpmigratereq, it can be changed concurrently. Thus, we need to add READONCE to its readers...

CVE-2022-49588

CVE-2022-49588 corresponds to a data-race in the Linux kernel’s TCP sysctl_migrate_req reader. The vulnerability arises from concurrent reading of sysctl_tcp_migrate_req, which could be changed during access. The fix adds READ_ONCE() to the readers to prevent races. Affected component is the kern...

CVE-2022-49588 tcp: Fix data-races around sysctl_tcp_migrate_req.

In the Linux kernel, the following vulnerability has been resolved: tcp: Fix data-races around sysctltcpmigratereq. While reading sysctltcpmigratereq, it can be changed concurrently. Thus, we need to add READONCE to its readers...

CVE-2022-49587 tcp: Fix a data-race around sysctl_tcp_notsent_lowat.

In the Linux kernel, the following vulnerability has been resolved: tcp: Fix a data-race around sysctltcpnotsentlowat. While reading sysctltcpnotsentlowat, it can be changed concurrently. Thus, we need to add READONCE to its reader...

CVE-2022-49587

The CVE-2022-49587 entry concerns a data-race in the Linux kernel related to reading sysctl_tcp_notsent_lowat, which could be modified concurrently. The fix is to add READ_ONCE() to the reader, addressing a sysctl data-race in the tcp stack. The vulnerability is rated with CVSS v3.1 metrics indic...

CVE-2022-49587 tcp: Fix a data-race around sysctl_tcp_notsent_lowat.

In the Linux kernel, the following vulnerability has been resolved: tcp: Fix a data-race around sysctltcpnotsentlowat. While reading sysctltcpnotsentlowat, it can be changed concurrently. Thus, we need to add READONCE to its reader...

CVE-2022-49585 tcp: Fix data-races around sysctl_tcp_fastopen_blackhole_timeout.

In the Linux kernel, the following vulnerability has been resolved: tcp: Fix data-races around sysctltcpfastopenblackholetimeout. While reading sysctltcpfastopenblackholetimeout, it can be changed concurrently. Thus, we need to add READONCE to its readers...

CVE-2022-49586

Technical details about CVE-2022-49586 are not provided in the connected documents. The sources only reiterate that the Linux kernel fix involved reading of sysctl_tcp_fastopen and a READ_ONCE() addition. Monitor for vendor updates.

CVE-2022-49580 ipv4: Fix a data-race around sysctl_fib_multipath_use_neigh.

In the Linux kernel, the following vulnerability has been resolved: ipv4: Fix a data-race around sysctlfibmultipathuseneigh. While reading sysctlfibmultipathuseneigh, it can be changed concurrently. Thus, we need to add READONCE to its reader...

CVE-2022-49579

In the Linux kernel, the following vulnerability has been resolved: ipv4: Fix data-races around sysctlfibmultipathhashpolicy. While reading sysctlfibmultipathhashpolicy, it can be changed concurrently. Thus, we need to add READONCE to its readers...

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-49579

CVE-2022-49579: In the Linux kernel, a data race around ipv4_fib_multipath_hash_policy was resolved by adding READ_ONCE() guards to readers of sysctl_fib_multipath_hash_policy. Affected component: kernel IPv4 multipath hash policy reader; root cause: concurrent modification during reads; impact: ...

CVE-2022-49580 ipv4: Fix a data-race around sysctl_fib_multipath_use_neigh.

In the Linux kernel, the following vulnerability has been resolved: ipv4: Fix a data-race around sysctlfibmultipathuseneigh. While reading sysctlfibmultipathuseneigh, it can be changed concurrently. Thus, we need to add READONCE to its reader...

CVE-2022-49579 ipv4: Fix data-races around sysctl_fib_multipath_hash_policy.

In the Linux kernel, the following vulnerability has been resolved: ipv4: Fix data-races around sysctlfibmultipathhashpolicy. While reading sysctlfibmultipathhashpolicy, it can be changed concurrently. Thus, we need to add READONCE to its readers...

CVE-2022-49579 ipv4: Fix data-races around sysctl_fib_multipath_hash_policy.

In the Linux kernel, the following vulnerability has been resolved: ipv4: Fix data-races around sysctlfibmultipathhashpolicy. While reading sysctlfibmultipathhashpolicy, it can be changed concurrently. Thus, we need to add READONCE to its readers...

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-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...