CVE-2022-50328
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 | to 5.10.150 (exc) |
| linux | linux_kernel | From 5.11 (inc) to 5.15.75 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 5.19.17 (exc) |
| linux | linux_kernel | From 6.0 (inc) to 6.0.3 (exc) |
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 issue in the Linux kernel's jbd2 component, specifically in the function 'jbd2_fc_wait_bufs'. The problem occurs because the code uses a buffer head ('bh') after its reference count has been decremented and potentially freed, which can lead to accessing freed memory. The fix involves checking if the buffer is up-to-date before decrementing the buffer head's reference count to avoid this unsafe use.
How can this vulnerability impact me? :
The use-after-free vulnerability could lead to undefined behavior such as system crashes, data corruption, or potential escalation of privileges if exploited. It affects the stability and security of the Linux kernel's journaling subsystem, which could impact system reliability and security.