Vulnerability · Published Dec 30, 2025 · Assigned by Linux
CVE-2022-50856cifs: Fix xid leak in cifs_ses_add_channel()
Unrated
In plain English
A 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 10% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Severity (CVSS )–Not rated
Exploit odds (30 days)0.2%top 90.2% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known
Official description
In the Linux kernel, the following vulnerability has been resolved: cifs: Fix xid leak in cifs_ses_add_channel() Before return, should free the xid, otherwise, the xid will be leaked.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| AlmaLinux:8 | bpftool | 4.18.0-553.82.1.el8_10 | ALSA-2025:19447 |
| AlmaLinux:8 | kernel | 4.18.0-553.82.1.el8_10 | ALSA-2025:19447 |
| AlmaLinux:8 | kernel-abi-stablelists | 4.18.0-553.82.1.el8_10 | ALSA-2025:19447 |
| AlmaLinux:8 | kernel-core | 4.18.0-553.82.1.el8_10 | ALSA-2025:19447 |
| AlmaLinux:8 | kernel-cross-headers | 4.18.0-553.82.1.el8_10 | ALSA-2025:19447 |
| AlmaLinux:8 | kernel-debug | 4.18.0-553.82.1.el8_10 | ALSA-2025:19447 |
| AlmaLinux:8 | kernel-debug-core | 4.18.0-553.82.1.el8_10 | ALSA-2025:19447 |
| AlmaLinux:8 | kernel-debug-devel | 4.18.0-553.82.1.el8_10 | ALSA-2025:19447 |
| AlmaLinux:8 | kernel-debug-modules | 4.18.0-553.82.1.el8_10 | ALSA-2025:19447 |
| AlmaLinux:8 | kernel-debug-modules-extra | 4.18.0-553.82.1.el8_10 | ALSA-2025:19447 |
| AlmaLinux:8 | kernel-devel | 4.18.0-553.82.1.el8_10 | ALSA-2025:19447 |
| AlmaLinux:8 | kernel-doc | 4.18.0-553.82.1.el8_10 | ALSA-2025:19447 |
| AlmaLinux:8 | kernel-headers | 4.18.0-553.82.1.el8_10 | ALSA-2025:19447 |
| AlmaLinux:8 | kernel-modules | 4.18.0-553.82.1.el8_10 | ALSA-2025:19447 |
| AlmaLinux:8 | kernel-modules-extra | 4.18.0-553.82.1.el8_10 | ALSA-2025:19447 |
| AlmaLinux:8 | kernel-tools | 4.18.0-553.82.1.el8_10 | ALSA-2025:19447 |
| AlmaLinux:8 | kernel-tools-libs | 4.18.0-553.82.1.el8_10 | ALSA-2025:19447 |
| AlmaLinux:8 | kernel-tools-libs-devel | 4.18.0-553.82.1.el8_10 | ALSA-2025:19447 |
| AlmaLinux:8 | kernel-zfcpdump | 4.18.0-553.82.1.el8_10 | ALSA-2025:19447 |
| AlmaLinux:8 | kernel-zfcpdump-core | 4.18.0-553.82.1.el8_10 | ALSA-2025:19447 |
| AlmaLinux:8 | kernel-zfcpdump-devel | 4.18.0-553.82.1.el8_10 | ALSA-2025:19447 |
| AlmaLinux:8 | kernel-zfcpdump-modules | 4.18.0-553.82.1.el8_10 | ALSA-2025:19447 |
| AlmaLinux:8 | kernel-zfcpdump-modules-extra | 4.18.0-553.82.1.el8_10 | ALSA-2025:19447 |
| AlmaLinux:8 | perf | 4.18.0-553.82.1.el8_10 | ALSA-2025:19447 |
| AlmaLinux:8 | python3-perf | 4.18.0-553.82.1.el8_10 | ALSA-2025:19447 |
| Debian:12 | linux | 6.0.6-1 | DEBIAN-CVE-2022-50856 |
| Debian:13 | linux | 6.0.6-1 | DEBIAN-CVE-2022-50856 |
| Debian:14 | linux | 6.0.6-1 | DEBIAN-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux | 5.15.0-60.66 | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1030.34 | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1033.40 | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1033.40.1 | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1029.36 | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1027.32 | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1015.19 | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1025.28 | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1025.30 | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1028.33 | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-60.66 | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1017.17 | UBUNTU-CVE-2022-50856 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1029.35 | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1024.26 | UBUNTU-CVE-2022-50856 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2022-50856 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2022-50856 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | d70e9fa55884760b6d6c293dbf20d8c52ce11fb7 – before 7286f875510486fdc2fc426b7c826262e2283a65d70e9fa55884760b6d6c293dbf20d8c52ce11fb7 – before 847301f0ee1c29f34cc48547ce1071990f24969cd70e9fa55884760b6d6c293dbf20d8c52ce11fb7 – before db2a8b6c17e128d91f35d836c569f4a6bda4471bd70e9fa55884760b6d6c293dbf20d8c52ce11fb7 – before e909d054bdea75ef1ec48c18c5936affdaecbb2c |
| Linux | Linux | 5.5 |