CVE-2022-49811 json
drbd: use after free in drbd_create_device()
published 2025-05-01 18 mo ago modified 2026-11-05 3 d ago also EUVD-2025-12957
- cvss
- 7.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 13%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
drbd: use after free in drbd_create_device()
The drbd_destroy_connection() frees the "connection" so use the _safe() iterator to prevent a use after free.
Patch / fix
- Linux Linux 4.14.300, 4.19.267, 5.4.225, 5.10.156, 5.15.80, 6.0.10, 6.1
- linux Debian 14, Debian 13, Debian 12 6.0.10-1
debian advisories DEBIAN-CVE-2022-49811
- linux Ubuntu 18.04 LTS 4.15.0-206.217
- linux Ubuntu 20.04 LTS 5.4.0-144.161
- linux Ubuntu 22.04 LTS 5.15.0-67.74
- linux-aws Ubuntu 18.04 LTS 4.15.0-1151.164
- linux-aws Ubuntu 20.04 LTS 5.4.0-1097.105
- linux-aws Ubuntu 22.04 LTS 5.15.0-1031.35
- linux-gcp Ubuntu 20.04 LTS 5.4.0-1101.110
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1030.37
ubuntu advisories UBUNTU-CVE-2022-49811
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel RHEL 9 5.14.0-362.8.1.el9_3
- rv RHEL 9 5.14.0-362.8.1.el9_3
- perf RHEL 9 5.14.0-362.8.1.el9_3
- rtla RHEL 9 5.14.0-362.8.1.el9_3
- bpftool RHEL 9 7.2.0-362.8.1.el9_3
- libperf RHEL 9 5.14.0-362.8.1.el9_3
- kernel-rt RHEL 9 5.14.0-362.8.1.el9_3
- kernel-64k RHEL 9 5.14.0-362.8.1.el9_3
red hat advisories RHSA-2023:6583
- git.kernel.org/stable/c/fc1897f16ebcfd22364f2afcc27f53a740f3bc7a commit
- git.kernel.org/stable/c/bf47ca1b35fc1f55091ffaff5fbe41ea0c6f59a1 commit
- git.kernel.org/stable/c/813a8dd9c45fd46f5cbbfbedf0791afa7740ccf5 commit
- git.kernel.org/stable/c/9ed51414aef6e59e832e2960f10766dce2d5b1a1 commit
- git.kernel.org/stable/c/7d93417d596402ddd46bd76c721f205d09d0d025 commit
- git.kernel.org/stable/c/c2a00b149836d60c222930bbea6b2139caf34d4f commit
- git.kernel.org/stable/c/a7a1598189228b5007369a9622ccdf587be0730f commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-49811 updated cvss 5.5
kernel: drbd: use after free in drbd_create_device()
-
Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 moreaffected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3 d ago
Exploit prediction
0.23% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-416 Use After Free
- Technology feeds
References
-
git.kernel.org
/stable/c/fc1897f16ebcfd22364f2afcc27f53a740f3bc7a
patch
-
git.kernel.org
/stable/c/bf47ca1b35fc1f55091ffaff5fbe41ea0c6f59a1
patch
-
git.kernel.org
/stable/c/813a8dd9c45fd46f5cbbfbedf0791afa7740ccf5
patch
-
git.kernel.org
/stable/c/9ed51414aef6e59e832e2960f10766dce2d5b1a1
patch
-
git.kernel.org
/stable/c/7d93417d596402ddd46bd76c721f205d09d0d025
patch
-
git.kernel.org
/stable/c/c2a00b149836d60c222930bbea6b2139caf34d4f
patch
-
git.kernel.org
/stable/c/a7a1598189228b5007369a9622ccdf587be0730f
patch
Sources
- CVE List CVE-2022-49811
- NVD CVE-2022-49811
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.