Vulnerability · Published Feb 26, 2025 · Assigned by Linux
CVE-2022-49637ipv4: Fix a data-race around sysctl_fib_sync_mem.
Medium 4.7
In plain English
A medium-severity race condition in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 8% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Severity (CVSS 3.1)4.7Medium
Exploit odds (30 days)0.2%top 92.4% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known
Official description
In the Linux kernel, the following vulnerability has been resolved: ipv4: Fix a data-race around sysctl_fib_sync_mem. While reading sysctl_fib_sync_mem, it can be changed concurrently. So, we need to add READ_ONCE() to avoid a data-race.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 5.18.14-1 | DEBIAN-CVE-2022-49637 |
| Debian:13 | linux | 5.18.14-1 | DEBIAN-CVE-2022-49637 |
| Debian:14 | linux | 5.18.14-1 | DEBIAN-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux | 5.15.0-50.56 | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1021.25 | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1021.26 | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1024.30.1 | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1019.25 | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1017.20 | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1004.6 | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1015.17 | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1017.22 | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1019.23 | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-50.56 | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1015.15 | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1019.24 | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1016.18 | UBUNTU-CVE-2022-49637 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2022-49637 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2022-49637 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 9ab948a91b2c2abc8e82845c0e61f4b1683e3a4f – before 7c1acd98fb221dc0d847451b9ab86319f8b9916c9ab948a91b2c2abc8e82845c0e61f4b1683e3a4f – before 418b191d5f223a8cb6cab09eae1f72c04ba6adf29ab948a91b2c2abc8e82845c0e61f4b1683e3a4f – before 9be8aac91960ea32fd0e874758c9afee665c57d29ab948a91b2c2abc8e82845c0e61f4b1683e3a4f – before 190cd4ff128373271e065afb20f1d2247b3f10c39ab948a91b2c2abc8e82845c0e61f4b1683e3a4f – before 73318c4b7dbd0e781aaababff17376b2894745c0 |
| Linux | Linux | 5.2 |
Weakness: CWE-362 · Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
References
- https://git.kernel.org/stable/c/7c1acd98fb221dc0d847451b9ab86319f8b9916c
- https://git.kernel.org/stable/c/418b191d5f223a8cb6cab09eae1f72c04ba6adf2
- https://git.kernel.org/stable/c/9be8aac91960ea32fd0e874758c9afee665c57d2
- https://git.kernel.org/stable/c/190cd4ff128373271e065afb20f1d2247b3f10c3
- https://git.kernel.org/stable/c/73318c4b7dbd0e781aaababff17376b2894745c0