CVE-2022-50488 json
block, bfq: fix possible uaf for 'bfqq->bic'
published 2025-10-04 13 mo ago modified 2026-10-15 24 d ago also EUVD-2025-32371
- 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 5%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
block, bfq: fix possible uaf for 'bfqq->bic'
Our test report a uaf for 'bfqq->bic' in 5.10:
================================================================== BUG: KASAN: use-after-free in bfq_select_queue+0x378/0xa30
CPU: 6 PID: 2318352 Comm: fsstress Kdump: loaded Not tainted 5.10.0-60.18.0.50.h602.kasan.eulerosv2r11.x86_64 #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.12.1-0-ga5cab58-20220320_160524-szxrtosci10000 04/01/2014 Call Trace: bfq_select_queue+0x378/0xa30 bfq_dispatch_request+0xe8/0x130 blk_mq_do_dispatch_sched+0x62/0xb0 __blk_mq_sched_dispatch_requests+0x215/0x2a0 blk_mq_sched_dispatch_requests+0x8f/0xd0 __blk_mq_run_hw_queue+0x98/0x180 __blk_mq_delay_run_hw_queue+0x22b/0x240 blk_mq_run_hw_queue+0xe3/0x190 blk_mq_sched_insert_requests+0x107/0x200 blk_mq_flush_plug_list+0x26e/0x3c0 blk_finish_plug+0x63/0x90 __iomap_dio_rw+0x7b5/0x910 iomap_dio_rw+0x36/0x80 ext4_dio_read_iter+0x146/0x190 [ext4] ext4_file_read_iter+0x1e2/0x230 [ext4] new_sync_read+0x29f/0x400 vfs_read+0x24e/0x2d0 ksys_read+0xd5/0x1b0 do_syscall_64+0x33/0x40 entry_SYSCALL_64_after_hwframe+0x61/0xc6
Commit 3bc5e683c67d ("bfq: Split shared queues on move between cgroups") changes that move process to a new cgroup will allocate a new bfqq to use, however, the old bfqq and new bfqq can point to the same bic:
1) Initial state, two process with io in the same cgroup.
Process 1 Process 2 (BIC1) (BIC2) | Λ | Λ | | | | V | V | bfqq1 bfqq2
2) bfqq1 is merged to bfqq2.
Process 1 Process 2 (BIC1) (BIC2) | | \-------------\| V bfqq1 bfqq2(coop)
3) Process 1 exit, then issue new io(denoce IOA) from Process 2.
(BIC2) | Λ | | V | bfqq2(coop)
4) Before IOA is completed, move Process 2 to another cgroup and issue io.
Process 2 (BIC2) Λ |\--------------\ | V bfqq2 bfqq3
Now that BIC2 points to bfqq3, while bfqq2 and bfqq3 both point to BIC2. If all the requests are completed, and Process 2 exit, BIC2 will be freed while there is no guarantee that bfqq2 will be freed before BIC2.
Fix the problem by clearing bfqq->bic while bfqq is detached from bic.
Patch / fix
- Linux Linux 5.5, 5.10.175, 5.15.86, 5.18, 5.19, 6.0.16, 6.1.2, 6.2
- linux Debian 14, Debian 13, Debian 12 6.1.4-1
debian advisories DEBIAN-CVE-2022-50488
- linux Ubuntu 22.04 LTS 5.15.0-69.76
- linux-aws Ubuntu 22.04 LTS 5.15.0-1033.37
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1031.38
- linux-gke Ubuntu 22.04 LTS 5.15.0-1030.35
- linux-ibm Ubuntu 22.04 LTS 5.15.0-1027.30
- linux-kvm Ubuntu 22.04 LTS 5.15.0-1030.35
- linux-azure Ubuntu 22.04 LTS 5.15.0-1035.42
- linux-gkeop Ubuntu 22.04 LTS 5.15.0-1017.22
ubuntu advisories UBUNTU-CVE-2022-50488
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
- 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-64kb SLES 15 SP5-LTSS, SLE High Performance Computing 15 SP5-LTSS, SLE High Performance Computing 15 SP5-ESPOS 5.14.21-150500.55.127.1
- kernel-syms SLES for SAP 15 SP5, SLES 15 SP5-LTSS, SLE High Performance Computing 15 SP5-LTSS +1 more 5.14.21-150500.55.127.1
- kernel-source SLES for SAP 15 SP5, SLES 15 SP5-LTSS, SLE Micro 5.5 +2 more 5.14.21-150500.55.127.1
- kernel-default SLES for SAP 15 SP5, SLES 15 SP5-LTSS, SLE Micro 5.5 +3 more 5.14.21-150500.55.127.1
suse advisories SUSE-SU-2026:0495-1SUSE-SU-2026:0475-1SUSE-SU-2025:4320-1SUSE-SU-2025:4188-1SUSE-SU-2025:4149-1SUSE-SU-2025:4139-1
- git.kernel.org/stable/c/5533742c7cb1bc9b1f0bf401cc397d44a3a9e07a commit
- git.kernel.org/stable/c/094f3d9314d67691cb21ba091c1b528f6e3c4893 commit
- git.kernel.org/stable/c/b22fd72bfebda3956efc4431b60ddfc0a51e03e0 commit
- git.kernel.org/stable/c/761564d93c8265f65543acf0a576b32d66bfa26a commit
- git.kernel.org/stable/c/64dc8c732f5c2b406cc752e6aaa1bd5471159cab 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-50488 updated cvss 6.0
kernel: block, bfq: fix possible uaf for 'bfqq->bic'
-
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
- total
- Assessed
- 24 d ago
Exploit prediction
0.17% chance of exploitation in the next 30 days, higher than 5% 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/5533742c7cb1bc9b1f0bf401cc397d44a3a9e07a
patch
-
git.kernel.org
/stable/c/094f3d9314d67691cb21ba091c1b528f6e3c4893
patch
-
git.kernel.org
/stable/c/b22fd72bfebda3956efc4431b60ddfc0a51e03e0
patch
-
git.kernel.org
/stable/c/761564d93c8265f65543acf0a576b32d66bfa26a
patch
-
git.kernel.org
/stable/c/64dc8c732f5c2b406cc752e6aaa1bd5471159cab
patch
Sources
- CVE List CVE-2022-50488
- NVD CVE-2022-50488
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.