Vulnerability · Published May 3, 2024 · Assigned by Linux
CVE-2022-48703thermal/int340x_thermal: handle data_vault when the value is ZERO_SIZE_PTR
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.
Official description
In the Linux kernel, the following vulnerability has been resolved: thermal/int340x_thermal: handle data_vault when the value is ZERO_SIZE_PTR In some case, the GDDV returns a package with a buffer which has zero length. It causes that kmemdup() returns ZERO_SIZE_PTR (0x10). Then the data_vault_read() got NULL point dereference problem when accessing the 0x10 value in data_vault. [ 71.024560] BUG: kernel NULL pointer dereference, address: 0000000000000010 This patch uses ZERO_OR_NULL_PTR() for checking ZERO_SIZE_PTR or NULL value in data_vault.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 5.19.11-1 | DEBIAN-CVE-2022-48703 |
| Debian:13 | linux | 5.19.11-1 | DEBIAN-CVE-2022-48703 |
| Debian:14 | linux | 5.19.11-1 | DEBIAN-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux | 5.15.0-156.166 | USN-7774-1 |
| Ubuntu:22.04:LTS | linux | 5.15.0-156.166 | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1092.99 | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1092.99 | USN-7774-1 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1096.105 | USN-7775-2 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1096.105 | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1096.105.1 | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1092.101 | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1092.101 | USN-7774-1 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1089.95 | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1089.95 | USN-7774-1 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1075.83 | USN-7774-1 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1075.83 | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1086.89 | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1086.89 | USN-7774-1 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1087.93 | USN-7774-1 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1087.93 | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1088.93 | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1088.93 | USN-7774-4 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-156.166 | USN-7774-1 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-156.166 | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1087.88 | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1087.88 | USN-7774-1 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1045.45 | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1045.45 | USN-7774-1 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1034.34 | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1034.34 | USN-7774-5 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1090.96 | USN-7774-1 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1090.96 | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1086.89 | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1086.89 | USN-7774-1 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1056.60 | UBUNTU-CVE-2022-48703 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1056.60 | USN-7774-1 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 0ba13c763aacb27ab32bde5d559bf40e88465921 – before 722588f17fd3d3a127e50718ec2caf22bd7e9daa0ba13c763aacb27ab32bde5d559bf40e88465921 – before 39d5137085a6c37ace4680ee4d24020a4a03e7dc0ba13c763aacb27ab32bde5d559bf40e88465921 – before dae42083b045a4ddf71c57cf350cb2412b5915c20ba13c763aacb27ab32bde5d559bf40e88465921 – before 7931e28098a4c1a2a6802510b0cbe57546d2049d |
| Linux | Linux | 5.8 |