Log in Start free

Vulnerability · Published Jun 18, 2025 · Assigned by Linux

CVE-2022-49973skmsg: Fix wrong last sg check in sk_msg_recvmsg()

Medium 5.5

In plain English

A medium-severity security flaw 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 16% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)5.5Medium
Exploit odds (30 days)0.2%top 84.5% 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: skmsg: Fix wrong last sg check in sk_msg_recvmsg() Fix one kernel NULL pointer dereference as below: [ 224.462334] Call Trace: [ 224.462394] __tcp_bpf_recvmsg+0xd3/0x380 [ 224.462441] ? sock_has_perm+0x78/0xa0 [ 224.462463] tcp_bpf_recvmsg+0x12e/0x220 [ 224.462494] inet_recvmsg+0x5b/0xd0 [ 224.462534] __sys_recvfrom+0xc8/0x130 [ 224.462574] ? syscall_trace_enter+0x1df/0x2e0 [ 224.462606] ? __do_page_fault+0x2de/0x500 [ 224.462635] __x64_sys_recvfrom+0x24/0x30 [ 224.462660] do_syscall_64+0x5d/0x1d0 [ 224.462709] entry_SYSCALL_64_after_hwframe+0x65/0xca In commit 9974d37ea75f ("skmsg: Fix invalid last sg check in sk_msg_recvmsg()"), we change last sg check to sg_is_last(), but in sockmap redirection case (without stream_parser/stream_verdict/ skb_verdict), we did not mark the end of the scatterlist. Check the sk_msg_alloc, sk_msg_page_add, and bpf_msg_push_data functions, they all do not mark the end of sg. They are expected to use sg.end for end judgment. So the judgment of '(i != msg_rx->sg.end)' is added back here.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.0.2-1DEBIAN-CVE-2022-49973
Debian:13linux6.0.2-1DEBIAN-CVE-2022-49973
Debian:14linux6.0.2-1DEBIAN-CVE-2022-49973
Ubuntu:22.04:LTSlinux5.15.0-57.63UBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-aws5.15.0-1027.31UBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-azure5.15.0-1030.37UBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1030.37.1UBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-gcp5.15.0-1026.33UBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-gke5.15.0-1024.29UBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1012.16UBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-ibm5.15.0-1022.25UBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1023.28UBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-kvm5.15.0-1025.30UBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-57.63UBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-oracle5.15.0-1026.32UBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-raspi5.15.0-1022.24UBUNTU-CVE-2022-49973
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2022-49973
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2022-49973
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2022-49973
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2022-49973

Affected products (as reported)

VendorProductVersions
Linux Linux 293c53b7dbf9073cbcc488f938bc053ff4caeec0 – before de22cba333d8699ad77e79f862fe1320cb1284de1295dae30f30c3daa03005ed8958d44b17f037fd – before 10ee118a1756141f8e9c87aa7344ed12b41630a89974d37ea75f01b47d16072b5dad305bd8d23fcc – before 583585e48d965338e73e1eb383768d16e0922d734674c0da448b546e390a981b819cd4af5cb16cf95.18.18 – before 5.19
Linux Linux 5.15.61 – before 5.15.665.19.2 – before 5.19.8

References