Vulnerability · Published Feb 26, 2025 · Assigned by Linux
CVE-2022-49366ksmbd: fix reference count leak in smb_check_perm_dacl()
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.3% (higher than 18% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix reference count leak in smb_check_perm_dacl() The issue happens in a specific path in smb_check_perm_dacl(). When "id" and "uid" have the same value, the function simply jumps out of the loop without decrementing the reference count of the object "posix_acls", which is increased by get_acl() earlier. This may result in memory leaks. Fix it by decreasing the reference count of "posix_acls" before jumping to label "check_access_bits".
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 5.18.5-1 | DEBIAN-CVE-2022-49366 |
| Debian:13 | linux | 5.18.5-1 | DEBIAN-CVE-2022-49366 |
| Debian:14 | linux | 5.18.5-1 | DEBIAN-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux | 5.15.0-48.54 | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1020.24 | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1020.25 | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1024.30.1 | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1018.24 | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1016.19 | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1003.5 | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1015.17 | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1016.21 | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1018.22 | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-48.54 | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1007.7 | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1018.23 | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1015.17 | UBUNTU-CVE-2022-49366 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2022-49366 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2022-49366 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 777cad1604d68ed4379ec899d1f7d2f6a29f01f0 – before cf824b95c12a1abacadbc2d069931963221a3414777cad1604d68ed4379ec899d1f7d2f6a29f01f0 – before 248d71b440aef829f5cc5f6545ca113ef5062900777cad1604d68ed4379ec899d1f7d2f6a29f01f0 – before 9758a6653c27867d810de02b4e5697163dda9883777cad1604d68ed4379ec899d1f7d2f6a29f01f0 – before d21a580dafc69aa04f46e6099616146a536b0724 |
| Linux | Linux | 5.15 |