CVE-2026-23168 Details
Description
In the Linux kernel, the following vulnerability has been resolved: flex_proportions: make fprop_new_period() hardirq safe Bernd has reported a lockdep splat from flexible proportions code that is essentially complaining about the following race: <timer fires> run_timer_softirq - we are in softirq context call_timer_fn writeout_period fprop_new_period write_seqcount_begin(&p->sequence); <hardirq is raised> ... blk_mq_end_request() blk_update_request() ext4_end_bio() folio_end_writeback() __wb_writeout_add() __fprop_add_percpu_max() if (unlikely(max_frac < FPROP_FRAC_BASE)) { fprop_fraction_percpu() seq = read_seqcount_begin(&p->sequence); - sees odd sequence so loops indefinitely Note that a deadlock like this is only possible if the bdi has configured maximum fraction of writeout throughput which is very rare in general but frequent for example for FUSE bdis. To fix this problem we have to make sure write section of the sequence counter is irqsafe.
A race condition vulnerability has been identified in the Linux kernel's flexible proportions code, specifically in the 'fprop_new_period' function. This vulnerability can lead to a deadlock situation where the function loops indefinitely, unable to complete its execution. The issue arises when a timer fires and the 'fprop_new_period' function is called to update a sequence counter. If a hard interrupt occurs during this process, it can disrupt the normal flow, causing the function to misinterpret the sequence state and get stuck. This deadlock scenario is particularly likely to occur with FUSE backends, where the writeout throughput is maximized, creating a perfect storm for the race condition to manifest.
The vulnerability has been addressed by modifying the 'fprop_new_period' function to ensure that the sequence counter is updated in a way that is safe from hard interrupts. Users should apply the latest patches available in the Linux kernel stable tree to mitigate this issue.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/0acc9ba7a1b5ba4d998c5753e709be904e179b75 | kernel.org | Patch |
| https://git.kernel.org/stable/c/78ede9ebd679dadf480dce6f7b798e3603f88348 | kernel.org | Patch |
| https://git.kernel.org/stable/c/884b2590ffcc7222cbbd6298051f4c243cc36f5d | kernel.org | Patch |
| https://git.kernel.org/stable/c/b91a84299d72ae0e05551e851e47cd3008bd025b | kernel.org | Patch |
| https://git.kernel.org/stable/c/dd9e2f5b38f1fdd49b1ab6d3a85f81c14369eacc | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.0, < 6.1.162 >= 6.2, < 6.6.123 >= 6.7, < 6.12.69 >= 6.13, < 6.18.9 6.19 rc1 6.19 rc2 6.19 rc3 6.19 rc4 6.19 rc5 6.19 rc6 6.19 rc7 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Mar 18, 2026 | Initial Analysis | [email protected] |
| Feb 14, 2026 | New CVE Received | kernel.org |