CVE-2022-50329
BaseFortify
Publication date: 2025-09-15
Last updated on: 2025-12-04
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 5.15.86 |
| linux | linux_kernel | 6.0.16 |
| linux | linux_kernel | 6.1.2 |
| linux | linux_kernel | 6.2 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a use-after-free (UAF) issue in the Linux kernel's BFQ (Budget Fair Queueing) block I/O scheduler. Specifically, the function bfq_exit_icq_bfqq() can free a bfqq object and then bic_set_bfqq() accesses this freed object, leading to a use-after-free condition. The fix involved reordering calls to ensure bfq_exit_bfqq() is called after bic_set_bfqq(), preventing access to freed memory.
How can this vulnerability impact me? :
The use-after-free vulnerability can lead to undefined behavior such as system crashes, data corruption, or potential escalation of privileges if exploited. This can affect system stability and security on Linux systems using the BFQ scheduler.