CVE-2022-50329 json
block, bfq: fix uaf for bfqq in bfq_exit_icq_bfqq
published 2025-09-15 13 mo ago modified 2026-10-15 24 d ago also EUVD-2022-55526
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 6%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
block, bfq: fix uaf for bfqq in bfq_exit_icq_bfqq
Commit 64dc8c732f5c ("block, bfq: fix possible uaf for 'bfqq->bic'") will access 'bic->bfqq' in bic_set_bfqq(), however, bfq_exit_icq_bfqq() can free bfqq first, and then call bic_set_bfqq(), which will cause uaf.
Fix the problem by moving bfq_exit_bfqq() behind bic_set_bfqq().
Patch / fix
- Linux Linux 5.15.87, 6.0.17, 6.1.3
- linux Debian 14, Debian 13, Debian 12 6.1.4-1
debian advisories DEBIAN-CVE-2022-50329
- 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
- kernel-rt SLE Micro 5.2 5.3.18-150300.235.1
- kernel-source-rt SLE Micro 5.2 5.3.18-150300.235.1
- kernel-default SLE Micro 5.2 5.3.18-150300.59.235.1
- kernel-default-base SLE Micro 5.2 5.3.18-150300.59.235.1.150300.18.140.1
- kernel-rt SLE Micro 5.5 5.14.21-150500.13.109.1
- kernel-source-rt SLE Micro 5.5 5.14.21-150500.13.109.1
- kernel-rt SLE Micro 5.4, SLE Micro 5.3 5.14.21-150400.15.133.1
- kernel-source-rt SLE Micro 5.4, SLE Micro 5.3 5.14.21-150400.15.133.1
suse advisories SUSE-SU-2026:0495-1SUSE-SU-2026:0475-1SUSE-SU-2025:3761-1SUSE-SU-2025:3716-1SUSE-SU-2025:03628-1SUSE-SU-2025:03615-1
- git.kernel.org/stable/c/1425f1bb5df5239021fd09ebc2a5e8070e705d36 commit
- git.kernel.org/stable/c/7949b0df3dd9f4817ed4a4e989fa9ee81df6205f commit
- git.kernel.org/stable/c/cfe5b38c37720313eff0dec5517442c7ab3c9a20 commit
- git.kernel.org/stable/c/1ed959fef5b1c6f1a7a3fbea543698c30ebd6678 commit
- git.kernel.org/stable/c/246cf66e300b76099b5dbd3fdd39e9a5dbc53f02 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-50329 updated cvss 6.7
kernel: Linux kernel: Denial of Service due to use-after-free in BFQ scheduler
-
Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 moreaffected: workaround, 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 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
- total
- Assessed
- 24 d ago
Exploit prediction
0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| 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/1425f1bb5df5239021fd09ebc2a5e8070e705d36
patch
-
git.kernel.org
/stable/c/7949b0df3dd9f4817ed4a4e989fa9ee81df6205f
patch
-
git.kernel.org
/stable/c/cfe5b38c37720313eff0dec5517442c7ab3c9a20
patch
-
git.kernel.org
/stable/c/1ed959fef5b1c6f1a7a3fbea543698c30ebd6678
patch
-
git.kernel.org
/stable/c/246cf66e300b76099b5dbd3fdd39e9a5dbc53f02
patch
Sources
- CVE List CVE-2022-50329
- NVD CVE-2022-50329
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.